Dotnetpanel Forums

Default SPS 3.0 and .net 3 install. Machine has been rebooted.I'm running DNP 2.0.3 (just upgraded).

When creating a new Sharepoint site, the following error occurs. 

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'ADD_SITE' task on 'sharepoint.xxxx.com.au' SHAREPOINT ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error while installing SharePoint:

at DotNetPark.DotNetPanel.Providers.SharePoint.Sps20.ExtendVirtualServer(SharePointSite site)
at DotNetPark.DotNetPanel.Server.SharePointServer.ExtendVirtualServer(SharePointSite site)
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at DotNetPark.DotNetPanel.Providers.SharePoint.SharePointServer.ExtendVirtualServer(SharePointSite site)
at DotNetPark.DotNetPanel.EnterpriseServer.SharePointServerController.AddSite(SharePointSite item)
--- End of inner exception stack trace ---
at DotNetPark.DotNetPanel.EnterpriseServer.SharePointServerController.AddSite(SharePointSite item)
at DotNetPark.DotNetPanel.EnterpriseServer.esSharePointServers.AddSharePointSite(SharePointSite item)
--- End of inner exception stack trace ---
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at DotNetPark.DotNetPanel.EnterpriseServer.esSharePointServers.AddSharePointSite(SharePointSite item)
at DotNetPark.DotNetPanel.Portal.SharePointEditSite.SaveItem()

 DNP event log says:

[1/16/2007 10:44:07 PM] ERROR: Can't ExtendVirtualServer 'Windows SharePoint Services 3.0' provider
System.Exception: Error while installing SharePoint:

   at DotNetPark.DotNetPanel.Providers.SharePoint.Sps20.ExtendVirtualServer(SharePointSite site)
   at DotNetPark.DotNetPanel.Server.SharePointServer.ExtendVirtualServer(SharePointSite site)
 

 

Check that web site for which you are trying to install WSS 3.0 is accessible via web browser. They have changed installation procedure in WSS 3.0 and seems it requires web site should be live.

Okay, I think you mean give it a proper DNS name? I think it has anyway, but I'll try anyway.

Does it matter it's on a subdomain? I've tried both subdomain and highest level domain, both report the same error.

 

Nope. still the same error when DNS is okay or not.

Sharepoint has created its own instance of SQL, will that effect the setup procedure inside DNP?

Its set to SERVERNAME\ Microsoft##SSEE. Do you have to create another SQL 2005 service in DNP?

 

mattcosa:

Nope. still the same error when DNS is okay or not.

Btw, what do you have in "Internal Address" and "External Address" fields on MSSQL service properties in DNP?

If there are "(local)\SQLEXPRESS" then it should be changed to "COMPUTER_NAME\SQLEXPRESS" where COMPUTER_NAME is the server name.

mattcosa:

Sharepoint has created its own instance of SQL, will that effect the setup procedure inside DNP?

Its set to SERVERNAME\ Microsoft##SSEE. Do you have to create another SQL 2005 service in DNP?

Nope, that's OK that it uses its own SQL Server instance (btw, it is SQL Server Embedded).

OK, then try to extend web site from the command line:

c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm -o extendvs -url http://localhost:9955 -ownerlogin FLASH\wss_test1 -owneremail wss_test2@mail.com -databaseserver FLASH\sqlexpress -databasename wss_test2 -databaseuser wss_test2 -databasepassword wss_test2

change command line parameters to appropriate ones. Let me know what it outputs.

Feodor Fitsner:

mattcosa:

Nope. still the same error when DNS is okay or not.

Btw, what do you have in "Internal Address" and "External Address" fields on MSSQL service properties in DNP?

If there are "(local)\SQLEXPRESS" then it should be changed to "COMPUTER_NAME\SQLEXPRESS" where COMPUTER_NAME is the server name.

mattcosa:

Sharepoint has created its own instance of SQL, will that effect the setup procedure inside DNP?

Its set to SERVERNAME\ Microsoft##SSEE. Do you have to create another SQL 2005 service in DNP?

Nope, that's OK that it uses its own SQL Server instance (btw, it is SQL Server Embedded).

Hi Feodor,

Yeh I just figured it was using embedded...

I specified the "External Address" as my proper IP. Previously I had left it to the value of (local).

Tried adding the site again and it added it okay, but nothing in the IIS webite directory, and the site has lost its configuration (no ASP version, dedicated application pool disabled).

Deleted all the sites in DNP cleaned up IIS and started again with he stsadm cmd; it reports:

The IIS Web Site you have selected is in use by SharePoint.  You must select another port or hostname.

Simply tried another site name (instead of the one I want), so I used the localhost:9955, now reports;

Login failed for user 'cleint_wss_dbuser'

WHich is the user I specified in the cmd.

stsadm -o extendvs -url http://localhost:9955 -ownerlogin COMPUTERNAME\client_wss_user -owneremail admin@client -databaseserver COMPUTERNAME -databasename cleint_wss_db -databaseuser cleint_wss_dbuser -databasepassword mypassword

 

 

'cleint_wss_dbuser' should exist in database and have db_creator rights. -url parameter web site should exist and can be opening in web browser.

All other parameters should be real too.

Does anyone have a guide to getting sharepoint 3.0 going with dotnetpanel? I'd be interested to sell this service to my customers, I had previously offered the old sharepoint and people paid a premium to use it. Looking at the problems in this thread I'm somewhat apprehensive to undertake this until it is solid in dotnetpanel....any feedback will help.

Feodor Fitsner:

'cleint_wss_dbuser' should exist in database and have db_creator rights. -url parameter web site should exist and can be opening in web browser.

All other parameters should be real too.

 

If the user exists, DNP reports with a " Specified database user already exists in the hosting space" error message (in yellow, rather than a red one).

 Tried in the command line, it reported:

Cannot open database "client_wss_db" requested by the login. The login failed. Login failed for user 'client_wss_dbuser'.

Manually created the database, then added the user to the databse (all through DNP); command line tool reported:
 

The specified database has an incorrect collation.  Rebuild the database with the Latin1_General_CI_AS_KS_WS collation or create a new database.

Tried modifiing the colllation through SQL Management studio, same result.

Deleted the cleint_wss_db through DNP. Manually granted the client_wss_dbuser db_creator rights through SQL Management Studio, and ran the command again:

The IIS Web Site has been extended.  You may need to use iisreset.exe to restart
 IIS before your site becomes accessible.

Operation completed successfully.

Please access the SharePoint site at http://xxx/.

 

Why doesn't DNP automatically grant the specified user db_creator rights when creating the user during WSS3 setup?

 

Went to the website URL: Doesn't work... Checked IIS management console and found that WSS had created a new site with no web site identification. Removed the web site identification from the site DNP created, and added it to the newly created website that WSS created and now it works.

Also noticed the setup has completely removed the dedicated application pool that was created for the site through DNP as well as disabled ASP.NET on the site.

I'm assuming that all this happened because the IIS site wasn't supposed to have been created before hand by DNP. Looks like DNP has a few issues still with WSS3.

Anybody else care to add any experiences?

 

amclint:

Does anyone have a guide to getting sharepoint 3.0 going with dotnetpanel? I'd be interested to sell this service to my customers, I had previously offered the old sharepoint and people paid a premium to use it. Looking at the problems in this thread I'm somewhat apprehensive to undertake this until it is solid in dotnetpanel....any feedback will help.

 

You could always pay for one support ticket and get them to fix it.... It's just the support tickets add up fairly quickly.

 I'd just like to have it going for proof of concept on a dev server, so when it goes live I KNOW it will work the way I want it too. Just not doing that either at the moment!
 

 

Hi,

I had trouble setting up SQL 2005 Express, got a error message but after some troubleshooting I found out that the "Network Service" account did not have any access to the "\SQL2005Databases" folder. Strange because DNP did manage to setup a subfolder dir with "user name". After adding the "Network Service" account in NTFS DNP where able to add databases but how can I use the SharePoint built-in database instead, the built-in database do not have any size limits as the Express Edition have.

Even thought I now can add DB I am still not able to create a SharePoint site, get the error message in yellow that the quota has exceeded but it has not. And another thing; why do you have to set up both SharePoint user and SQL DB user to add a SharePoint site and also why do I have to type the database name can't we just get a drop-box?

Kind Regards,
raja

piraya:

Hi,

I had trouble setting up SQL 2005 Express, got a error message but after some troubleshooting I found out that the "Network Service" account did not have any access to the "\SQL2005Databases" folder. Strange because DNP did manage to setup a subfolder dir with "user name". After adding the "Network Service" account in NTFS DNP where able to add databases but how can I use the SharePoint built-in database instead, the built-in database do not have any size limits as the Express Edition have.

Personally, I wouldn't use the WSS SQL service as its SQL embedded edition, and as you said, there is NO control over this database through DNP.

piraya:

Even thought I now can add DB I am still not able to create a SharePoint site, get the error message in yellow that the quota has exceeded but it has not. And another thing; why do you have to set up both SharePoint user and SQL DB user to add a SharePoint site and also why do I have to type the database name can't we just get a drop-box?

Kind Regards,
raja

The sharepoint user is for logging into the actual sharepoint website and administering it. You will have to add a user everytime you want somebody to be able to access the site in any way, or post information via email attachments.

I think there is also a bit of confusion with the SQL database. I'm still not sure if DNP automatically sets up the database for Sharepoint (it should, hence why there is no drop down box for a list of DBs because you are creating a new one). Unfortunately, DNP doesnt assign db_creator access to the user specified during setup and it bombs out trying to extend the virtual server.
 

 

 

mattcosa:

piraya:

Hi,

I had trouble setting up SQL 2005 Express, got a error message but after some troubleshooting I found out that the "Network Service" account did not have any access to the "\SQL2005Databases" folder. Strange because DNP did manage to setup a subfolder dir with "user name". After adding the "Network Service" account in NTFS DNP where able to add databases but how can I use the SharePoint built-in database instead, the built-in database do not have any size limits as the Express Edition have.

Personally, I wouldn't use the WSS SQL service as its SQL embedded edition, and as you said, there is NO control over this database through DNP.

piraya:

Even thought I now can add DB I am still not able to create a SharePoint site, get the error message in yellow that the quota has exceeded but it has not. And another thing; why do you have to set up both SharePoint user and SQL DB user to add a SharePoint site and also why do I have to type the database name can't we just get a drop-box?

Kind Regards,
raja

The sharepoint user is for logging into the actual sharepoint website and administering it. You will have to add a user everytime you want somebody to be able to access the site in any way, or post information via email attachments.

I think there is also a bit of confusion with the SQL database. I'm still not sure if DNP automatically sets up the database for Sharepoint (it should, hence why there is no drop down box for a list of DBs because you are creating a new one). Unfortunately, DNP doesnt assign db_creator access to the user specified during setup and it bombs out trying to extend the virtual server.

"Database name" is a textbox, but not a dropdown, because SharePoint creates a new database itself during site installation. If you get a yellow warning then you should increase hosting plan quotas for database users and databases.

When you installing WSS site DNP does grant db_creator permissions to the specified database user, otherwise STSADM won't work.

Looking at the error regarding database collation I think the problem might be exactly in that.

Frankly speaking guys, the problem of WSS 3.0 STSADM tool is that it does not output command execution results to standard console output and thus the message can't be intersepted by DNP and shown in the exception.

If you like you can e-mail us RDC details to your server and the panel URL. Then we'll be able to investigate what causes those errors. It's not a support ticket, but we like to be sure WSS 3.0 works with DNP and then write an installation/setup guide. You can help other customers

Thanks for replying Feodor, 

Feodor Fitsner:

When you installing WSS site DNP does grant db_creator permissions to the specified database user, otherwise STSADM won't work.

Looking at the error regarding database collation I think the problem might be exactly in that.

This is what I suspected as well, but I not 100% sure. Only the experts can be like you guys!

Origionally I though DNP wasn't creating the user at all, but it just wasn't specifying db_creator permissions on that user.

Feodor Fitsner:

Frankly speaking guys, the problem of WSS 3.0 STSADM tool is that it does not output command execution results to standard console output and thus the message can't be intersepted by DNP and shown in the exception.

If you like you can e-mail us RDC details to your server and the panel URL. Then we'll be able to investigate what causes those errors. It's not a support ticket, but we like to be sure WSS 3.0 works with DNP and then write an installation/setup guide. You can help other customers

Makes life difficult without the program talking!

I'd be happy to help out, the server I'm working on is a dev server for a replacement hosting system. I'll fwd the RDC details to support@dotnetpanel.com.

 

Update for anybody interested WSS3.

I've let Feodor in to have a play with my server to run some tests;

On my setup, WSS has basically given up extending websites correctly. It also refuses to recognize new IIS websites when adding either through DNP or manually using the IIS console.

Tried re-installing the product, and the installation failed before creating a new WSS database manualy using psconfig –cmd configdb –create -database. WSS is still not extending websites or behaving correctly, so back to square one here.

May have to format sever as it's basically a waste of everybody's time at the moment. To clarify also, this is of no fault of the DNP team or Feodor, it just happened.

Has anybody had any success with WSS3 and DNP 2.0.3? Any comments please.