Sharepoint 2010 and Website Panel

Question

First off, love this product. Been using it for a year now for web/mail/exchange /hosting, works great.

Now I would like to add a Sharepoint hosting package. I know it cannot be incorporated with Exchange /hosting but I have gone through all the steps to setup a hosted organization and such, but am stuck on the site collection creation.

Organization creates fine, users creates fine, site collection gives me:

"Service item could not be created/updated
You can not create or update service item because the required resource is not available in the current hosting space."

I have looked through all the services and cannot track down what is missing. I think it may be a dns config issue but I can find a log or audit to track it down. The above error is a yellow warning but I cannot create a site. On the virtual server: OS, IIS, Sharepoint is on sharepoint server, --- DNS, HO is on Domain Controller. 

Answer 1

I think you forgot to mention what service / vendor you are using. If its vendor related, then you may want to ask this question to specific vendor.

 

Thank you.

---

Karim Roumani
PortalFront - Complete SharePoint Hosting Solutions

Answer 2

Microsoft Sharepoint 2010 Foundation

Website Panel 1.2

Answer 3

Anybody think of what I may have missed?

Answer 4

Hi Karim,

I have exactly the same problem as you, and no way to find a way to solve the problem.

I have applied the Framework4 fix with referralCache.config, but no way

Jean-Yves

Answer 5

Me too. The problem for me occured after upgrading to 1.2 not realising it would break SharePoint!!!!!!!

The error before applying the fix was that sharepoint didn't support .net4 so I applied the fix like you did from the following link:

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

Now I am getting:

"Service item could not be created/updated
You can not create or update service item because the required resource is not available in the current hosting space."

So this has to be something to do with the Framework fix.

I need to get an answer on this one desperately - Pavel anyone?

Do we need to make any changes to the servers\virtual servers??

Obviously I should of tested the SharePoint side of things before deploying!

TIA

Adam

Answer 6

I found the answer! :)

So when you edit the referralcache, you need to do this for both the old website listening on 9003 and the new on 9004. Once I changed the file for the original website everything worked!

Panic over and I hope this helps others.

Adam

Answer 7

I tried your solution, but I still have the same error when I try to create a Site Collection:

Task Details
Source:  HOSTEDSHAREPOINT
Task Name: GET_LANGUAGES
Item Name:
User:  Admin
Started: 4/28/2012 2:09:38 PM
Finished: 4/28/2012 2:09:39 PM
Duration: 00:00:00
Severity: Error
Execution Log: 00:00:00

Client found response content type of 'text/html', but expected 'text/xml'.
The request failed with the error message:
--
Server Error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
--.
 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.Providers.HostedSolution.HostedSharePointServer.GetSupportedLanguages()
 at WebsitePanel.EnterpriseServer.Code.SharePoint.HostedSharePointServerController.GetSupportedLanguages(Int32 packageId)

Answer 8

Isn't this a different error from the original one? are you still seeing the error as per the Ops original post?

Answer 9

Everyone to resolve this error above I recommend upgrading to version 1.2.1 that was released earlier this month. We have moved the Server Component back to Framework 2.0. Even with the referal cache fix there were tons of issues when the entire server was not in 2.0 for anything powershell driven (WSP uses powershell to control most of the enterprise items include VPS management. When you execute a command with code running in 4.0 unexpected issues arise. This no longer is a problem in the latest release since WSP no longer is running in 4.0. I am currently looking into a solution like this that could also fix the issue allowing us to move back to the 4.0 framework on the server component in the future.

http://gallery.technet.microsoft.com/scriptcenter/Allow-PowerShell-V2-access-525799cc

---

Omar Armenteros Virtuworks