none
Sharepoint 2010 .NET Framework 4 and WebsitePanel 1.2.0

    Question

  • Since installing Websitepanel 1.2.0 on all my servers, Sharepoint no longer works.

    Here is the error message I get when accessing anything SPF2010 related, i.e. creating site collections, deleting site collections, etc:

    System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'DELETE_SITE' task on 'http://site.domain.com' HOSTEDSHAREPOINT ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Failed to delete site collection. ---> Microsoft SharePoint is not supported with version 4.0.30319.235 of the Microsoft .Net Runtime

    Any suggestions to get this working again?

    mardi 19 juillet 2011 15:43

Réponses

  • Hi Pavel, hoping for some good news on this today.

    Hi there,

    Yep, there are some... Please find a link to the article that provides instructions on workaround how to apply this: http://websitepanel.codeplex.com/wikipage?title=How%20To%20Run%20Hosted%20Solution%20Services%20with%20WebsitePanel%20v1.2.0.

    Your feedback is highly appreciated!


    Please vote, if you find a post helpful! Appreciate.
    • Marqué comme réponse rynoster mardi 9 août 2011 08:09
    lundi 8 août 2011 20:20
  • Ok sorry for the spam....

     

    Have found the cause of the problem. Before I configured this workaround, I deleted all WSP Services from my SharePoint server and reinstalled it all. I created a new sharepoint-wspserver domain service account during the setup. I did not give this account permissions to the SharePoint databases.

    After going through everything from scratch I set the new domain account up correct as per the documentation and it is now working correctly.

     

    If I go onto my SQL Server and remove the permissions for my domain account to the SharePoint databases (SharePoint_AdminContent, SharePoint_Config and HostedRoot) I get the same error again. Add them back in and it all works fine....

     

    Cheers

     

    jeudi 11 août 2011 11:54
  • jimhendo, our issue ended up being memory. Added memory and everything started working.

    Thanks Pavel!


    hypervhost
    jeudi 11 août 2011 19:16

Toutes les réponses

  • Same problem here. Cannot create or delete site collections.

     

    My SharePoint 2010 is RTM not SP1 yet, will try to update.... 

    mardi 19 juillet 2011 16:10
  • I upgraded to Sharepoint 2010 SP1 last night, no difference. I also installed the June 2010 cumulative update, same thing.
    mercredi 20 juillet 2011 06:29
  • Can any other 1.2.0 users confirm this behaviour or is this isolated?

    I just need to know how to proceed, thanks.

    jeudi 21 juillet 2011 13:32
  • I hope that fix will be available soon, this issue was submitted to WSP`s bug tracker, please see: http://websitepanel.codeplex.com/workitem/12
    samedi 23 juillet 2011 09:39
  • For now we are manually creating the sitecollections. Here is the details on creating site collection with hostheads: http://technet.microsoft.com/en-us/library/cc424952.aspx

     

    Once its fixed, we will use the rather complicated CRM Org Import instructions in this thread, but apply to SharePoint users instead. I have tested this and it works. Lucky we don't sell many SharePoint sites :p

     

    http://social.msdn.microsoft.com/Forums/en-US/wspentsupport/thread/9501f646-8f1b-4423-ba67-4c6d38c19b0f

     

     

    samedi 23 juillet 2011 16:02
  • I hope that fix will be available soon, this issue was submitted to WSP`s bug tracker, please see: http://websitepanel.codeplex.com/workitem/12

    I hope so too, I logged the bug. :)

    Can everyone please go this URL and vote so that this can be resolved sooner?

    dimanche 24 juillet 2011 07:52
  • For now we are manually creating the sitecollections. Here is the details on creating site collection with hostheads: http://technet.microsoft.com/en-us/library/cc424952.aspx

     

    Once its fixed, we will use the rather complicated CRM Org Import instructions in this thread, but apply to SharePoint users instead. I have tested this and it works. Lucky we don't sell many SharePoint sites :p

     

    http://social.msdn.microsoft.com/Forums/en-US/wspentsupport/thread/9501f646-8f1b-4423-ba67-4c6d38c19b0f

     

     

    Indeed, have been doing this as well, but resellers get upset if they want to quickly create a Sharepoint site 22:00 at night like they are used to and now have to rely on us to manually do it. Having the "Supports Sharepoint 2010" on Websitepanel means it should remain supported during upgrades.

    The CRM Org import instructions were actually done by me. I have actually improved the procedure since then, with no feedback in that thread I didn't think anyone actually used it. The main difference with the new procedure is mainly with the import of users using the WSP import tool to first import the users and then do the rest of the procedure.

    Anyway, the Sharepoint import is much simpler though, have that documented as well, see below. This was done with WSS still but should be similar to SPF2010.

    1. In command prompt, cd\ & cd "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN"
    2. stsadm -o setsitelock -url http://wspdemo.mysite.com -lock noaccess
    3. stsadm -o backup -url http://wspdemo.mysite.com -filename c:\backups\wspdemobak.bak -overwrite
    4. stsadm -o deletesite -url http://wspdemo.mysite.com
    5. Create site on control panel
    6. stsadm -o restore -url http://wspdemo.mysite.com -filename c:\backups\wspdemobak.bak -hostheaderwebapplicationurl http://sharepoint.mysite.com -overwrite
    7. stsadm -o setsitelock -url http://wspdemo.mysite.com -lock none
    8. stsadm -o setsiteuseraccountdirectorypath -url http://wspdemo.mysite.com -path ""

    dimanche 24 juillet 2011 08:01
  • I hope that fix will be available soon, this issue was submitted to WSP`s bug tracker, please see: http://websitepanel.codeplex.com/workitem/12

    I hope so too, I logged the bug. :)

    Can everyone please go this URL and vote so that this can be resolved sooner?

    I have tried to downgrade WSP to version 1.1.2 it was working for me previously. I did this by replacing files in tmp folder while installation via auto installer, but the problem that I`ve got now is that I can`t get Portal working. Maybe somebody have any ideas how to do downgrade it correctly, or maybe install previous version?
    redRat
    lundi 25 juillet 2011 03:08
  • For now we are manually creating the sitecollections. Here is the details on creating site collection with hostheads: http://technet.microsoft.com/en-us/library/cc424952.aspx

     

    Once its fixed, we will use the rather complicated CRM Org Import instructions in this thread, but apply to SharePoint users instead. I have tested this and it works. Lucky we don't sell many SharePoint sites :p

     

    http://social.msdn.microsoft.com/Forums/en-US/wspentsupport/thread/9501f646-8f1b-4423-ba67-4c6d38c19b0f

     

     

    Indeed, have been doing this as well, but resellers get upset if they want to quickly create a Sharepoint site 22:00 at night like they are used to and now have to rely on us to manually do it. Having the "Supports Sharepoint 2010" on Websitepanel means it should remain supported during upgrades.

    The CRM Org import instructions were actually done by me. I have actually improved the procedure since then, with no feedback in that thread I didn't think anyone actually used it. The main difference with the new procedure is mainly with the import of users using the WSP import tool to first import the users and then do the rest of the procedure.

    Anyway, the Sharepoint import is much simpler though, have that documented as well, see below. This was done with WSS still but should be similar to SPF2010.

    1. In command prompt, cd\ & cd "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN"
    2. stsadm -o setsitelock -url http://wspdemo.mysite.com -lock noaccess
    3. stsadm -o backup -url http://wspdemo.mysite.com -filename c:\backups\wspdemobak.bak -overwrite
    4. stsadm -o deletesite -url http://wspdemo.mysite.com
    5. Create site on control panel
    6. stsadm -o restore -url http://wspdemo.mysite.com -filename c:\backups\wspdemobak.bak -hostheaderwebapplicationurl http://sharepoint.mysite.com -overwrite
    7. stsadm -o setsitelock -url http://wspdemo.mysite.com -lock none
    8. stsadm -o setsiteuseraccountdirectorypath -url http://wspdemo.mysite.com -path ""

    It has been very helpful thank you! After working through, it gives a much better understanding of how the DB works.

     

     

    lundi 25 juillet 2011 21:16
  • this is very likely due to the fact that WSP now requires .NET 4 

    the SharePoint object model is not accessable from .NET 4 code what-so-ever.

    See the following blog:

    http://www.learningsharepoint.com/2010/08/21/net-4-with-sharepoint-foundation-2010/

    Not sure if there is a good solution, maybe they will have to revert back to 3.5.

    lundi 25 juillet 2011 23:06
  • I have unmarked the marked answer which had nothing to do with the actual problem. Please address the problem then we can start looking at marking answers.

    @EricJJohnson, that would be correct yes, this does not help us however. See this link - http://www.websitepanel.net/works-with

    It still states SPF 2010 is supported, not the case at all...

    Please go to the following link vote so that this issue can be addressed sooner.

    http://websitepanel.codeplex.com/workitem/12

    mardi 26 juillet 2011 06:01
  • I have rebuilt websitepanel installer v.1.0, now it downloads version 1.0 during initial installation, maybe it will be useful for somebody, for restoring "downgrading" WSP. After installation of the 1.0 version you can easily upgrade WSP to the needed version.

    You can download WSP installer 1.0 from sourceforge, install it, and then replace installer`s exe file with this file.

    Please test it somewhere before use, it helped me to restore missed funtionality.


    redRat
    mercredi 27 juillet 2011 05:44
  • I have rebuilt websitepanel installer v.1.0, now it downloads version 1.0 during initial installation, maybe it will be useful for somebody, for restoring "downgrading" WSP. After installation of the 1.0 version you can easily upgrade WSP to the needed version.

    You can download WSP installer 1.0 from sourceforge, install it, and then replace installer`s exe file with this file.

    Please test it somewhere before use, it helped me to restore missed funtionality.


    redRat

    Did you keep your old database?

    Did you downgrade Enterprise, Portal as well Server portions?

    mercredi 27 juillet 2011 10:02
  • I have rebuilt websitepanel installer v.1.0, now it downloads version 1.0 during initial installation, maybe it will be useful for somebody, for restoring "downgrading" WSP. After installation of the 1.0 version you can easily upgrade WSP to the needed version.

    You can download WSP installer 1.0 from sourceforge, install it, and then replace installer`s exe file with this file.

    Please test it somewhere before use, it helped me to restore missed funtionality.


    redRat

    Did you keep your old database?

    Did you downgrade Enterprise, Portal as well Server portions?

    DB - Nope, I`ve got test installation, but I hope SQL dump will help to restore it, at least you will be able to restore data manually by parts in case something went wrong. 

    Soft - Yes, patched installer will download all the parts v1.0 

    My case - I have got 1.1.0. I just removed everything, then installed all soft v1.0 from scratch with patched WSP installer. Then removed patched exe and updated everything till 1.1.0 (NOTE: do not allow installer update itself automagically, it will be updated till 1.2.0, just install 1.1.0 installer version from sourceforge when needed). 


    redRat
    mercredi 27 juillet 2011 11:06
  • Dear Microsoft,

     

    Could you please comment on this? Are you looking at fixing it? Should we roll back to 1.x? I see the bug tracked on codeplex is set to low impact.

     

    Would be a shame to roll back, the features in 1.2 are great.

     

    mercredi 27 juillet 2011 18:07
  • Dear Microsoft,

     

    Could you please comment on this? Are you looking at fixing it? Should we roll back to 1.x? I see the bug tracked on codeplex is set to low impact.

     

    Would be a shame to roll back, the features in 1.2 are great.

     

    Quite a disgrace really. I logged this bug with high impact.

    We do need more votes though.... Please guys, vote here - http://websitepanel.codeplex.com/workitem/12

    The inherent risk of downgrading is not really an option and I'm sure for most here as well. I find it quite distasteful that no one has responded to this to give an official answer, at least a glimmer of hope is better than no news at all...


    jeudi 28 juillet 2011 09:38

  • Dear Microsoft,

     

    Could you please comment on this? Are you looking at fixing it? Should we roll back to 1.x? I see the bug tracked on codeplex is set to low impact.

     

    Would be a shame to roll back, the features in 1.2 are great.

     

    Quite a disgrace really. I logged this bug with high impact.

    We do need more votes though.... Please guys, vote here - http://websitepanel.codeplex.com/workitem/12

    The inherent risk of downgrading is not really an option and I'm sure for most here as well. I find it quite distasteful that no one has responded to this to give an official answer, at least a glimmer of hope is better than no news at all...


    +1
    lundi 1 août 2011 06:46
  • Quite a disgrace really. I logged this bug with high impact.

     

    At the risk of being on the receiving end of some criticisim .. this is not a bug .. but it is definitely a disgrace.

    It's not a bug, because any developer worth his salt would either already be aware that SharePoint 2010 (all versions) does not respond to anything to do with .Net Framework 4 in any way, shape or form, or he would do his homework first, to ensure that the framework version he's migrating our entire management control panel will actually work with one of the core products we provide to our customers!

    What this debacle tells me is that not a single developer did any testing of any kind with any SharePoint 2010 installation. Otherwise they'd have known this upgrade would not work.  I'm sorry guys, but that's an epic failure.

    Now before you jump up and down on me, I totally agree that it's an astonishingly backward decision on Microsoft's part to build one of their core 2010 servers on anything but .Net Framework 4 when every other server in the range has been. And it's even more astonishing that they'd be pushing the .Net Framework 4 updates to us via MS Update, knowing that SharePoint won't work with it.

    But I believe this mess should flag three things:

    1. More work needs to be done to ensure that any new version of WSP is truly production-ready before it's released as being supposedly production-ready. My primary WSP installation is now riddled with errors as a result of the upgrade to WSP 1.2.0.

    2. The WSP development team MUST, as a matter of urgent priority, start work on providing a proven and reliable method of enabling flawless downgrading in the event of problems like those that have eventuated from this situation.

    3. The WSP development team need to exercise more detailed due diligence before releasing an updated version, because a flawed decision such as this one can potentially cost hundreds, if not thousands of service providers around the world, a lot of money in lost business and damaged reputations, and untold hours of wasted behind-the-scenes work trying to fix someone else's mistake.

    So, I have two requests; one for each separate group ...

    Microsoft: Please get busy ensuring that SharePoint 2010 (all versions) will actually respond to all communication from .Net Framework 4 and release an updated version of SharePoint 2010 (all versions) ASAP.

    WSP Development Team: Do your homework more thoroughly before you release an upgrade. Remember, there's a lot of people relying on your work. We greatly appreciate all your efforts, but WSP now being Open Source should never equate to "all care, but no responsibility taken".







    mardi 2 août 2011 11:21
  • Quite a disgrace really. I logged this bug with high impact.

     

    At the risk of being on the receiving end of some criticisim .. this is not a bug .. but it is definitely a disgrace.

    It's not a bug, because any developer worth his salt would either already be aware that SharePoint 2010 (all versions) does not respond to anything to do with .Net Framework 4 in any way, shape or form. Or, he would do his homework first, to ensure that the framework version he's migrating our entire management control panel will actually work with one of the core products we provide to our customers!

    What this debacle tells me is that not a single developer did any testing of any kind with any SharePoint 2010 installation. Otherwise they'd have known this upgrade would not work.  I'm sorry guys, but that 's en epic failure.

    Now before you jump up and down on me, I totally agree that it's an astonishingly backward decision on Microsoft's part to build one of their core 2010 servers on anything but .Net Framework 4 when every other server in the range has been. And it's even more astonishing that they'd be pushing the .Net Framework 4 updates to us via MS Update, knowing that SharePoint won't work with it.

    But I believe this mess should flag three things:

    1. More work needs to be done to ensure that any new version of WSP is truly production-ready before it's released as being supposedly production-ready. My primary WSP installation is now riddled with errors as a result of the upgrade to WSP 1.2.0.

    2. The WSP development team MUST, as a matter of urgent priority, start work on providing a proven and reliable method of enabling flawless downgrading in the event of problems like those that have eventuated from this situation.

    3. The WSP development team need to exercise more detailed due diligence before releasing an updated version, because a flawed decision such as this one can potentially cost hundreds, if not thousands of service providers around the world, a lot of money in lost business and damaged reputations, and untold hours of wasted behind-the-scenes work trying to fix someone else's mistake.

    So, I have two requests; one for each separate group ...

    Microsoft: Please get busy ensuring that SharePoint 2010 (all versions) will actually respond to all communication from .Net Framework 4 and release an updated version of SharePoint 2010 (all versions) ASAP.

    WSP Development Team: Do your homework more thoroughly before you release an upgrade. Remember, there's a lot of people relying on your work. We greatly appreciate all your efforts, but WSP now being Open Source should never equate to "all care, but no responsibility taken".




    Couldn't have said it better!!! +1 !!!!
    mardi 2 août 2011 11:28
  • Hi everyone,

    Thanks for sharing your feedback and thoughts on that issue! We are currently working to resolve that problem with SharePoint 2010 service provider on v1.2.0 and will provide you with an update on this shortly.

     


    Please vote, if you find a post helpful! Appreciate.
    mercredi 3 août 2011 18:35
  • Hi everyone,

    Thanks for sharing your feedback and thoughts on that issue! We are currently working to resolve that problem with SharePoint 2010 service provider on v1.2.0 and will provide you with an update on this shortly.

     


    Please vote, if you find a post helpful! Appreciate.

    Thanks Pavel, that is great news indeed!

    Could you perhaps give a rough ETA? Are we talking days or weeks?

    jeudi 4 août 2011 07:01
  • Hi there,

    We are talking about a couple of days for the patch to be available.

    Thank you for your understanding and cooperation!


    Please vote, if you find a post helpful! Appreciate.
    jeudi 4 août 2011 17:21
  • Hey everyone,

    We've got an update on this!

    We came up with a workaround for the issue and currently testing it with one of our support partners. So, hopefully by Monday we'll receive a positive feedback from the partner and make the solution publicly available for everyone.

    Thank you for your patience and cooperation!


    Please vote, if you find a post helpful! Appreciate.
    samedi 6 août 2011 01:09
  • Hi Pavel, hoping for some good news on this today.
    lundi 8 août 2011 12:52
  • Hi Pavel, hoping for some good news on this today.

    Hi there,

    Yep, there are some... Please find a link to the article that provides instructions on workaround how to apply this: http://websitepanel.codeplex.com/wikipage?title=How%20To%20Run%20Hosted%20Solution%20Services%20with%20WebsitePanel%20v1.2.0.

    Your feedback is highly appreciated!


    Please vote, if you find a post helpful! Appreciate.
    • Marqué comme réponse rynoster mardi 9 août 2011 08:09
    lundi 8 août 2011 20:20
  • Thank you Pavel!!! I have implemented the solution and the initial tests look great, I am able to create and delete site collections again through the control panel.

    Just a few things I would like to comment on the solution instructions:

    1. The binaries from Hosted Solution v3.5.zip to do not overwrite the files in the newly created WSP (Hosted Solution)\bin folder created. I had to manually overwrite the files because I had errors. Not a problem, but maybe just document or get the Powershell script to do it.
    2. The documentation does not mention where the referralCache.config file needs to reside. This might be confusing with the now 2 sites. It has to go in the original Websitepanel\Server directory.

    Other than that, I am happy, thanks again to you and the partner who assisted in this solution!

    mardi 9 août 2011 08:09
  • Thank you Pavel!!! I have implemented the solution and the initial tests look great, I am able to create and delete site collections again through the control panel.

    Just a few things I would like to comment on the solution instructions:

    1. The binaries from Hosted Solution v3.5.zip to do not overwrite the files in the newly created WSP (Hosted Solution)\bin folder created. I had to manually overwrite the files because I had errors. Not a problem, but maybe just document or get the Powershell script to do it.
    2. The documentation does not mention where the referralCache.config file needs to reside. This might be confusing with the now 2 sites. It has to go in the original Websitepanel\Server directory.

    Other than that, I am happy, thanks again to you and the partner who assisted in this solution!

    Hey! You are always more than welcome!

    Thanks for your feedback! It's invaluable!


    Please vote, if you find a post helpful! Appreciate.
    mardi 9 août 2011 21:21
  • By the way, just uploaded new script to the article according to your feedback!

    Thanks again!


    Please vote, if you find a post helpful! Appreciate.
    mardi 9 août 2011 22:54
  • Unfortunately not working for us.
    Ran through all the steps (no errors).

    Am now testing adding a sharepoint site collection and get:

    Server was unable to process request. ---> Error executing 'ADD_SITE_COLLECTION' task on 'http://url-deleted.com' HOSTEDSHAREPOINT ---> Client found response content type of 'text/html', but expected 'text/xml'. The request failed with the error message: --


    Tried a few things to resolve including checking permissions, making sure both websitepanel sites are loading without errors.
    Not seeing any further errors or details in the wsp Enterprise or wsp server log.

    Any ideas?


    hypervhost
    mercredi 10 août 2011 15:25
  • @hypervhost

    Have you configured static routes in <WebsitePanel Server>\referralCache.config file appropriately?

    Thanks.


    Please vote, if you find a post helpful! Appreciate.
    mercredi 10 août 2011 17:21
  • Yes, absolutely and checked them again (tested the URLs within the file as well to make sure they were valid and working)
    That file was placed in the original c:\websitepanel\server folder
    hypervhost
    mercredi 10 août 2011 17:28
  • Yes, absolutely and checked them again (tested the URLs within the file as well to make sure they were valid and working)
    That file was placed in the original c:\websitepanel\server folder
    hypervhost

    Okay.

    I am curious what you will see if try to open http://<WSP 9004>/HostedSharePointServer.asmx in the browser?

    Thanks.


    Please vote, if you find a post helpful! Appreciate.
    mercredi 10 août 2011 17:33
  • I get a page with the list of services available:

    HostedSharePointServer
    The following operations are supported. For a formal definition, please review the Service Description.

    AppendTempFileBinaryChunk
    BackupSiteCollection
    CalculateSiteCollectionsDiskSpace
    etc....


    hypervhost
    mercredi 10 août 2011 17:41
  • I get a page with the list of services available:

    HostedSharePointServer
    The following operations are supported. For a formal definition, please review the Service Description.

    AppendTempFileBinaryChunk
    BackupSiteCollection
    CalculateSiteCollectionsDiskSpace
    etc....


    hypervhost

    Great!

    What will you see if you try to open http://<WSP 9003>/HostedSharePointServer.asmx in the browser?

    Thanks.


    Please vote, if you find a post helpful! Appreciate.
    mercredi 10 août 2011 17:43
  • Sorry, I honestly thought I had tested all those links but I guess I must have done only the port 9004 ones.
    This is throwing:

    WSE003: The input was not a valid SOAP message.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.NotSupportedException: WSE003: The input was not a valid SOAP message.

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [NotSupportedException: WSE003: The input was not a valid SOAP message.]
      Microsoft.Web.Services3.Messaging.SoapHttpRouter.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback callback, Object extraData) +183
      System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +405
      System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +375
    


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1


    hypervhost
    mercredi 10 août 2011 18:07
  • @hypervhost,

    Not - that is not a sign you did something wrong. Because this is the sign that everything is configured correctly. Since you turned on WSE routing that is okay to see that message - it means the routing works as expected.

    Well, then I have to ask you for access to the environment if that is possible.

    Thanks.


    Please vote, if you find a post helpful! Appreciate.
    mercredi 10 août 2011 18:11
  • Sure, do we have to submit a ticket with Microsoft or do you have a direct contact email?
    hypervhost
    mercredi 10 août 2011 18:20
  • @hypervhost,

    info (_a_t_) websitepanel (_do_t _ ) net.


    Please vote, if you find a post helpful! Appreciate.
    mercredi 10 août 2011 18:23
  • Hi Pavel,

    After running the PS script I cannot load http://wspserver:9004, i get:

     

    --------------------------------------------------------------------------------

    Configuration Error 

    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. 

     

    Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive.

    Source Error: 

    Line 62:       <soapServerProtocolFactory type="Microsoft.Web.Services3.WseProtocolFactory, Microsoft.Web.Services3" />

    Line 63:     </webServices>

    Line 64:     <compilation debug="true" targetFramework="4.0" />

    Line 65:   </system.web>

    Line 66:   <!-- WSE 3.0 settings -->

     

    If I change the "WebsitePanel Server Pool (Hosted Solution)" to use ASP 4.0 I can browse to the site, but I then get the exact same errors that hypervhost does above. Did you manage to find a solution to his problem?

     

    mercredi 10 août 2011 21:19
  • So i removed "<compilation debug="true" targetFramework="4.0" />" from my web.config and I can run the app pool in 2.0 now, but still receive the same errors when I try to create a site collection as hypervhost above

     

    also when I try to view the disk usage on an exsisting site collection I get a similar error:

     

    Error recalculating disk size. See audit log for more details. 



    Server was unable to process request. ---> Error executing 'CALCULATE_DISK_SPACE' task on '' HOSTED_SHAREPOINT ---> Client found response content type of 'text/html', but expected 'text/xml'. The request failed with the error message: --

    Server Error

    <fieldset style="padding-top: 5px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px;">

    500 - Internal server error.

    There is a problem with the resource you are looking for, and it cannot be displayed.

    </fieldset>

    mercredi 10 août 2011 21:50
  • jimhendo, I had to do the same as you with the same results. I have sent an email to Pavel. I'll let you know what our progress is.
    hypervhost
    mercredi 10 août 2011 21:57
  • So i removed "<compilation debug="true" targetFramework="4.0" />" from my web.config and I can run the app pool in 2.0 now, but still receive the same errors when I try to create a site collection as hypervhost above

     

    also when I try to view the disk usage on an exsisting site collection I get a similar error:

     

    Error recalculating disk size. See audit log for more details. 



    Server was unable to process request. ---> Error executing 'CALCULATE_DISK_SPACE' task on '' HOSTED_SHAREPOINT ---> Client found response content type of 'text/html', but expected 'text/xml'. The request failed with the error message: --

    Server Error

    <fieldset style="padding-top: 5px; padding-right: 10px; padding-bottom: 10px; padding-left: 10px;">

    500 - Internal server error.

    There is a problem with the resource you are looking for, and it cannot be displayed.

    </fieldset>

     

    I recall having a similar issue. The issue was resolved when I changed the referralcache.config settings, i.e. find and replace 127.0.0.1 with the actual IP address of the server.
    jeudi 11 août 2011 05:42
  • I have triple checked the referralcache.config settings, it is in the root of my exsisitng "C:\WebsitePanel\Server" and all of the IP addresses are correct, they match the bindinds in IIS7 and I can browse to the sites with the same results as hypervhost.

     

    rynoster, did you also have to remove the line 4.0 line from your web config? I have a brand new Websitepanel/Server directory after playing around with it last week trying to get it to work I deleted everything and started from scratch on this server. The default web.config it gave me has this 4.0 setting in it??

     

    Thanks hypervhost it will be very much appreciated.

    jeudi 11 août 2011 07:41
  • I have triple checked the referralcache.config settings, it is in the root of my exsisitng "C:\WebsitePanel\Server" and all of the IP addresses are correct, they match the bindinds in IIS7 and I can browse to the sites with the same results as hypervhost.

     

    rynoster, did you also have to remove the line 4.0 line from your web config? I have a brand new Websitepanel/Server directory after playing around with it last week trying to get it to work I deleted everything and started from scratch on this server. The default web.config it gave me has this 4.0 setting in it??

     

    Thanks hypervhost it will be very much appreciated.

    I was only required to edit the referralcache.config file with the IP address of the actual server. The only other issue I had was the files in the bin directory were not the latest ones from the download link, I had to manually copy them.

    Also, on which server are you installing this?

    jeudi 11 août 2011 08:16
  • This is on my dedicated SharePoint server, no other services are on here. I have the portal and enterprise servers on separate servers.

     

    jeudi 11 août 2011 10:35
  • This is on my dedicated SharePoint server, no other services are on here. I have the portal and enterprise servers on separate servers.

     

    Ok, that's correct then. The only other thing I did to my Sharepoint servers lately was upgrade them to SP1 and install the June Cumulative Update.

    Did this some time ago, so no idea if this could be related, highly doubt it though.

    jeudi 11 août 2011 10:37
  • Ok I have not yet upgraded to SP1 will do so tonight.

     

    One Q, When you browse to http://wspserver:9003/HostedSharePointServer.asmx do you get the same error as hypervhost above? Or do you get a list or operations like when you browse to it on 9004 ?

     

     

    jeudi 11 août 2011 10:59
  • Errrmmm... well i have no idea what I did to fix this but it is now working fine.

     

     

     

    Cheers :)

    jeudi 11 août 2011 11:43
  • Ok sorry for the spam....

     

    Have found the cause of the problem. Before I configured this workaround, I deleted all WSP Services from my SharePoint server and reinstalled it all. I created a new sharepoint-wspserver domain service account during the setup. I did not give this account permissions to the SharePoint databases.

    After going through everything from scratch I set the new domain account up correct as per the documentation and it is now working correctly.

     

    If I go onto my SQL Server and remove the permissions for my domain account to the SharePoint databases (SharePoint_AdminContent, SharePoint_Config and HostedRoot) I get the same error again. Add them back in and it all works fine....

     

    Cheers

     

    jeudi 11 août 2011 11:54
  • @jimhendo,

    Thanks a lot for the update! Nice analysis sketch though! :-)


    Please vote, if you find a post helpful! Appreciate.
    jeudi 11 août 2011 17:46
  • jimhendo, our issue ended up being memory. Added memory and everything started working.

    Thanks Pavel!


    hypervhost
    jeudi 11 août 2011 19:16
  • @hypervhost,

    You are always more than welcome!


    Please vote, if you find a post helpful! Appreciate.
    jeudi 11 août 2011 19:22
  • Thanks for this. Finally I was able to make it work in my virtual environment. I got some 503 errors. But they went off after I resetting the APP POOL Identity again from the IIS Manager.
    lundi 15 août 2011 18:35
  • Hi there,

    http://websitepanel.codeplex.com/wikipage?title=How%20To%20Run%20Hosted%20Solution%20Services%20with%20WebsitePanel%20v1.2.0

    Successfully Tested/Confirmed 100%.

    Please feel free to ask for advice/assistance.

    Thank you.


    Best regards, Dmitry Fitsner Support@ExpertServices.us | WebsitePanel Installations, Support & Consulting | Enterprise Solutions Planning & Deployment & Support. Website: ExpertServices.us ---ORDER ANY ENTERPRISE DEPLOYMENT AND GET A SECOND 25%-100% FREE !!!
    jeudi 18 août 2011 00:18
  • Quite a disgrace really. I logged this bug with high impact.

     

    At the risk of being on the receiving end of some criticisim .. this is not a bug .. but it is definitely a disgrace.

    It's not a bug, because any developer worth his salt would either already be aware that SharePoint 2010 (all versions) does not respond to anything to do with .Net Framework 4 in any way, shape or form. Or, he would do his homework first, to ensure that the framework version he's migrating our entire management control panel will actually work with one of the core products we provide to our customers!

    What this debacle tells me is that not a single developer did any testing of any kind with any SharePoint 2010 installation. Otherwise they'd have known this upgrade would not work.  I'm sorry guys, but that 's en epic failure.

    Now before you jump up and down on me, I totally agree that it's an astonishingly backward decision on Microsoft's part to build one of their core 2010 servers on anything but .Net Framework 4 when every other server in the range has been. And it's even more astonishing that they'd be pushing the .Net Framework 4 updates to us via MS Update, knowing that SharePoint won't work with it.

    But I believe this mess should flag three things:

    1. More work needs to be done to ensure that any new version of WSP is truly production-ready before it's released as being supposedly production-ready. My primary WSP installation is now riddled with errors as a result of the upgrade to WSP 1.2.0.

    2. The WSP development team MUST, as a matter of urgent priority, start work on providing a proven and reliable method of enabling flawless downgrading in the event of problems like those that have eventuated from this situation.

    3. The WSP development team need to exercise more detailed due diligence before releasing an updated version, because a flawed decision such as this one can potentially cost hundreds, if not thousands of service providers around the world, a lot of money in lost business and damaged reputations, and untold hours of wasted behind-the-scenes work trying to fix someone else's mistake.

    So, I have two requests; one for each separate group ...

    Microsoft: Please get busy ensuring that SharePoint 2010 (all versions) will actually respond to all communication from .Net Framework 4 and release an updated version of SharePoint 2010 (all versions) ASAP.

    WSP Development Team: Do your homework more thoroughly before you release an upgrade. Remember, there's a lot of people relying on your work. We greatly appreciate all your efforts, but WSP now being Open Source should never equate to "all care, but no responsibility taken".




    Couldn't have said it better!!! +1 !!!!

    Yes, software providers should be testing their product prior to release.

    No, you should not hold the developers responsible for an update you failed to test internally before deploying to your production systems. Do the testing yourself, verify it works in _your_ environment and THEN update. Don't blame others for you own mistakes.

    We are in the same boat, with the exception that it's in our lab environment and we're working on fixing it there before updating the production servers.

    jeudi 17 novembre 2011 16:40
  • Hi there,

    http://websitepanel.codeplex.com/wikipage?title=How%20To%20Run%20Hosted%20Solution%20Services%20with%20WebsitePanel%20v1.2.0

    Successfully Tested/Confirmed 100%.

    Please feel free to ask for advice/assistance.

    Thank you.


    Best regards, Dmitry Fitsner Support@ExpertServices.us | WebsitePanel Installations, Support & Consulting | Enterprise Solutions Planning & Deployment & Support. Website: ExpertServices.us ---ORDER ANY ENTERPRISE DEPLOYMENT AND GET A SECOND 25%-100% FREE !!!
    Hiya, i have applied the files according to the information however i get this while adding a sharepoint collection: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'ADD_SITE_COLLECTION' task on 'https://demo.simplicityexchange.com' HOSTEDSHAREPOINT ---> System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.NullReferenceException: Object reference not set to an instance of an object. Server stack trace: at WebsitePanel.Providers.HostedSolution.HostedSharePointServerImpl.CreateSiteCollection(Uri rootWebApplicationUri, SharePointSiteCollection siteCollection) 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.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 WebsitePanel.Providers.HostedSolution.HostedSharePointServerImpl.CreateSiteCollection(Uri rootWebApplicationUri, SharePointSiteCollection siteCollection) at WebsitePanel.Providers.HostedSolution.HostedSharePointServer.<>c__DisplayClass5.b__4(HostedSharePointServerImpl impl) at WebsitePanel.Providers.HostedSolution.HostedSharePointServer.ExecuteSharePointAction[TReturn](SharePointAction`1 action) at WebsitePanel.Providers.HostedSolution.HostedSharePointServer.CreateSiteCollection(SharePointSiteCollection siteCollection) at WebsitePanel.Server.HostedSharePointServer.<>c__DisplayClass6.b__5() at WebsitePanel.Server.HostedSharePointServer.ExecuteAction[TReturn](Action`1 action, String actionName) at WebsitePanel.Server.HostedSharePointServer.CreateSiteCollection(SharePointSiteCollection siteCollection) --- 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 WebsitePanel.EnterpriseServer.Code.SharePoint.HostedSharePointServerController.AddSiteCollection(SharePointSiteCollection item) --- End of inner exception stack trace --- at WebsitePanel.EnterpriseServer.Code.SharePoint.HostedSharePointServerController.AddSiteCollection(SharePointSiteCollection item) --- End of inner exception stack trace ---
    dimanche 11 décembre 2011 22:21