Dotnetpanel Forums

Thanks for that tip, I get rid of that behaviour by deleting the default holding page. I am going to do a fresh run from scratch this morning.

Would be interesting to see how people are setting up SP on the server so we are all on the same page though.

I did an advanced install, new web farm, single server install. That way it would not use the embedded sql server.

YES!!

I have no idea what I did differently this time but I have a 100% working installation.

I decided to use a new domain even though the one I was testing on had been deleted and reinstalled several times, includinging verifying the actual files on the server were gone.

To be sure, I logged into DNP from my workstattion as a regular user.

• Created the domain
• Created the web site
• Created a SP user
• Created a SP group and assigned the user to it
• IN DNP file manager, deleted default.aspx
• created the SP site
• opened IE7 to the domain, logged in with created user
• back to DNP, create another SP user
• back to the SP site and added new user
• logged in to SP with the 2nd created user

I did NOT change the app pool. Everything was done as a non admin in DNP over the inet.

Feodor: Just a suggestion. The default holding page is an aspx page. This is not necessary and causes confusion for SharePoint installation. I created a new plan without asp.net and it still uses the default.aspx holding page which won't work anyway. Change the holding page to index.htm so it can be read by all languages as well as not interfere with a SharePoint installation. Good job on the SP update. Forgive my last comments, I was getting frustrated.

squorpeeon:

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'ADD_SITE' task on 'charlottevisitorguide.com' SHAREPOINT ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error creating SharePoint site ---> System.Exception: Could not create SharePoint site, because web site root folder does not exist. Open web site properties and click "Update" button to re-create site folder.
at DotNetPark.DotNetPanel.Providers.SharePoint.Sps30Remote.ExtendVirtualServer(SharePointSite site)
--- End of inner exception stack trace ---

Server stack trace:
at DotNetPark.DotNetPanel.Providers.SharePoint.Sps30Remote.ExtendVirtualServer(SharePointSite site)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at DotNetPark.DotNetPanel.Providers.SharePoint.Sps30Remote.ExtendVirtualServer(SharePointSite site)
at DotNetPark.DotNetPanel.Providers.SharePoint.Sps30.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()

I did try to update as the error says, no go. Site root is there.

Make sure web site root folder is not locked. Also, try to install SharePoint on some other web site and see if it makes the difference.

prodigy:

I have tried to install as a stand alone and as a web-front. I am running SQL Server 2005 Standard. So far I have not been able to get 3.0 working at all. Are you supposed to install as stand-alone or web-front? 

here is one of the errors:

System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'ADD_SITE' task on 'aznozone.com' SHAREPOINT ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error creating SharePoint site ---> System.ArgumentException: (local) is an invalid or loopback address. Specify a valid server address.
at Microsoft.SharePoint.Administration.SPServer.ValidateAddress(String address)
at Microsoft.SharePoint.Administration.SPServer..ctor(String address, SPFarm farm, Guid id)
at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(Guid newDatabaseId, String strDatabaseServer, String strDatabaseName, String strDatabaseUsername, String strDatabasePassword, Int32 warningSiteCount, Int32 maximumSiteCount, Int32 status, Boolean provision, Boolean allowUpgrade)
at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(String strDatabaseServer, String strDatabaseName, String strDatabaseUsername, String strDatabasePassword, Int32 warningSiteCount, Int32 maximumSiteCount, Int32 status, Boolean provision, Boolean allowUpgrade)
at Microsoft.SharePoint.Administration.SPContentDatabaseCollection.Add(String strDatabaseServer, String strDatabaseName, String strDatabaseUsername, String strDatabasePassword, Int32 warningSiteCount, Int32 maximumSiteCount, Int32 status)
at Microsoft.SharePoint.Administration.SPWebApplication.CreateDefaultInstance(SPWebService service, Guid id, String applicationPoolId, IdentityType identityType, String applicationPoolUsername, SecureString applicationPoolPassword, String iisServerComment, Boolean secureSocketsLayer, String iisHostHeader, Int32 iisPort, Boolean iisAllowAnonymous, DirectoryInfo iisRootDirectory, Uri defaultZoneUri, Boolean iisEnsureNTLM, Boolean createDatabase, String databaseServer, String databaseName, String databaseUsername, String databasePassword, SPSearchServiceInstance searchServiceInstance, Boolean isPaired, Boolean autoActivateFeatures)
at Microsoft.SharePoint.Administration.SPWebApplicationBuilder.Create()
at DotNetPark.DotNetPanel.Providers.SharePoint.Sps30Remote.ExtendVirtualServer(SharePointSite site)
--- End of inner exception stack trace ---

Server stack trace:
at DotNetPark.DotNetPanel.Providers.SharePoint.Sps30Remote.ExtendVirtualServer(SharePointSite site)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at DotNetPark.DotNetPanel.Providers.SharePoint.Sps30Remote.ExtendVirtualServer(SharePointSite site)
at DotNetPark.DotNetPanel.Providers.SharePoint.Sps30.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()  

On "MS SQL" service properties in DNP change "(local)" to computer name for "External Address". To get WSS 3.0 work properly you should avoid usinng "(local)" when referencing SQL Server instance.

Taylex:

YES!!

I have no idea what I did differently this time but I have a 100% working installation.

I decided to use a new domain even though the one I was testing on had been deleted and reinstalled several times, includinging verifying the actual files on the server were gone.

To be sure, I logged into DNP from my workstattion as a regular user.

• Created the domain
• Created the web site
• Created a SP user
• Created a SP group and assigned the user to it
• IN DNP file manager, deleted default.aspx
• created the SP site
• opened IE7 to the domain, logged in with created user
• back to DNP, create another SP user
• back to the SP site and added new user
• logged in to SP with the 2nd created user

I did NOT change the app pool. Everything was done as a non admin in DNP over the inet.

Feodor: Just a suggestion. The default holding page is an aspx page. This is not necessary and causes confusion for SharePoint installation. I created a new plan without asp.net and it still uses the default.aspx holding page which won't work anyway. Change the holding page to index.htm so it can be read by all languages as well as not interfere with a SharePoint installation. Good job on the SP update. Forgive my last comments, I was getting frustrated.

Woof, at least someone has got it working! Thanks for your feedback! Btw, you can change the name of parking page on Web policies page: http://help.dotnetpanel.com/Administrator%20Guide/Account%20Policies/Web%20Policy.aspx 

I've spend last nights fighting with WSS 3.0 installation/uninstallation and its new API. Yes, on clean installation everything works OK, but problems come after first uninstallation/re-installation of WSS. Two problems here are: 1) how to correctly remove SQL Server 2005 embedded edition bundled with WSS and 2) how to correctly remove WSS. Hopefully, I found several HOWTOs on the Internet which I'll share with you on Monday.

Some notes regarding implementing WSS 3.0 in DNP:

1. Do not use "(local)" or "(local)\SQLExpress" in "External Address" field on "MS SQL" properties page. Use machine name or IP address instead, e.g. "SERVER1\SQLExpress", "SERVER1", "34.45.3.1", etc.

2. SharePoint site works good in both shared or dedicated pool, so it's unnecessary to change pool of SharePoint site in IIS admin pool right after provisioning.

Just thought I would chime in here real quick to report that I have now successfully set up a combination of 20 or so SP sites and subsites, added and removed users, groups and features, etc. All are working flawlessly. I'll give it a couple days and lots of playing around but I feel confident I can now host SharePoint on DNP.

i had to change the application pool to get it to work.

prodigy:

i had to change the application pool to get it to work.

That's strange. I am just using the default 2.0 pool. Not changing anything which is what you want since a regular user will not be able to change that app pool. Let's see if we can figure out what the difference is. I suspect it may be in the SQL Server user.

Hi all, I've been MIA over the last couple days - work has a priority over devel!


Anyway. Feodor + DNP team, thanks for getting this SPS3 API in so quickly, I hope in some way my dev server was help. Only comment is perhaps a BETA tag next time as somebody else suggested would be appropriate next time.
 

Taylex:

To be sure, I logged into DNP from my workstattion as a regular user.

• Created the domain
• Created the web site
• Created a SP user
• Created a SP group and assigned the user to it
• IN DNP file manager, deleted default.aspx
• created the SP site
• opened IE7 to the domain, logged in with created user
• back to DNP, create another SP user
• back to the SP site and added new user
• logged in to SP with the 2nd created user

I did NOT change the app pool. Everything was done as a non admin in DNP over the inet.

Thanks for the run down there. These are exactly the same steps I took basically. I had two major problems, one of which was similar to yours;

    - default holding page interfering

    - SPS would not start until it was moved into the SPS app pool.

    - When creating users I had to first create them in DNP sharepoint users, then add them manually to SPS.  

Feodor Fitsner:

2. SharePoint site works good in both shared or dedicated pool, so it's unnecessary to change pool of SharePoint site in IIS admin pool right after provisioning.

 Ill try some more installs see if there are any different results.
 

mattcosa: The user does have to be added in DNP before you can add it in sharepoint. That is by design, the SP user must have a machine account first as SP will not create it.

Here is what I think is happening with the APP Pools. The default App pool runs as Network Service, The SP pool runs as Local System. Could one of you who have the app pool problem verify that your SQL server is running as Local System? If it is, try changing it to Network Service and see if that fixes your issue.

One more quick note, the backup and restore SP function in DNP works great, even with a domain name change.

Hi Matt,

Your help with clean development machine are very appreciated, thank you!

You may rename parking page on web policy settings. For now you should add users and groups in DNP and then manually in WSS.

The only concern I have at the moment is application pool. I'm just wondering why it should be changed to make WSS site working?

Feodor Fitsner:

The only concern I have at the moment is application pool. I'm just wondering why it should be changed to make WSS site working?

It doesn't, at least not on all installs. I am not changinging mine and others are so lets try to figure out the difference before you start rewriting the provider.

Yes, you're right

I've just installed WSS 3. 0 on a new server with a new download of DNP server. After a tussle getting WSS 3.0 to actually install properly there was no issue with DNP creating new sites - the only thing I need to change was the holding page to a .htm one instead of .aspx. DNP didn't seem to have any issue with the standard SQL database install and again no issue when I moved the default setting off the embedded version across to our dedicated setup.

Great job again DNP.

Cheers,

Mark 

kantona:

I've just installed WSS 3. 0 on a new server with a new download of DNP server. After a tussle getting WSS 3.0 to actually install properly there was no issue with DNP creating new sites - the only thing I need to change was the holding page to a .htm one instead of .aspx. DNP didn't seem to have any issue with the standard SQL database install and again no issue when I moved the default setting off the embedded version across to our dedicated setup.

Great job again DNP.

Cheers,

Mark 

Thanks for the feedback, Mark!