26 เมษายน 2555 14:00
I've installed sharepoint foundation 2010 in a Windows server 2008 R2 standard environment. I've added some site collections and added some libraries to the site pages. Ive put in various permissions and groups and tested no problem using Sharepoint workspace 2010 on a Windows 7 32 bit client.
But when I do a remote desktop connection to another server with 2008 R2 standard installed I can't get Sharepoint workspace 2010 to work properly. It opens an account and connects to my sharepont site but in the pane to the right where I would normally see library documents listed all that comes up is an error stating - Error: Cannot Display Tool.
Also if I try to sync I get the following error:-
The parameter is incorrect
HResult: 0x80070057 (0x386d7565)
Process: Groove.exe (ID:17936(0x00004610))
No amount of googling has found a solution, no similar postings had any resolutions.
Any help would be much appreciated
21 พฤษภาคม 2555 19:06
Did you ever resolve this issue? A few customers have seen this error when the SharePoint web application does not have a root site, although it is not the standard error for that situation. The absence of a root site will prevent SharePoint Workspace from syncing any subsites.
Let me know if this helps or not.
22 พฤษภาคม 2555 10:47
issue still happening - the problem only happens when remote desktoping to a Server 2008 R2 machine then on that machine opening an account in Sharepoint workspace and connecting to sites I've set up. The account opens, connection runs through the usual sycing to libraries etc but when opening the newly created workspace I get the above described errors. The exact same process works fine from a 32 bit workstation running windows7 ie I'm able to connect and do all the usual things through workspace, so if it was the root problem surely I would have problems on the 32 bit workstation as well.
When setting up sharepoint foundation a default site was created which I've left as is. I created a new web app then site collection and under that collection 3 sites on the same level. I've not set up any sub sites yet.
Thanks for the reply, it seems advice on Sharepoint Foundation is very sparce. Let me know if you have any more info.
22 พฤษภาคม 2555 17:17
My apologies. I'd focused on the error and hadn't adequately read the information you provided on the environment. The issue is probably with using SharePoint Workspace on the remote computer, not with SharePoint Foundation.
Here is what I understand you to be doing:
- You use Remote Desktop to connect to the Windows Server 2008 R2 computer, where you log in with your domain account, which is a member of the local Users group.
- On the remote computer, you start SharePoint Workspace.
- On the Launchbar, you click New, click SharePoint Workspace, select your site, and then click OK.
- The workspace is created and appears (from the progress bar) to download content.
- When you click Open Workspace, no content is displayed. Instead, you see the "Cannot Display Tool" error.
Is that correct?
There are three areas where SharePoint Workspace is complicated to run remotely:
- Where SharePoint Workspace will be run by a user other than the one installing it, it must not be lauched during the installation. This seems the most likely to be the issue, as we have seen the same failure and error at a customer site where several users had been given a computer image created on a computer where SharePoint Workspace had been launched before image creation.
- Only one user should run SharePoint Workspace (Groove.exe) at a time. (Sometimes multiple instances work, but it's not reliable.)
- You need to have a local profile on the computer which is running SharePoint Workspace. SharePoint Workspace is not supported with Roaming or Temporary profiles. Usually, this problem would prevent you from starting SharePoint Workspace, but some environments with custom permissions can lead to other errors.
- SharePoint Workspace uses the current user's permissions for SharePoint server access, In the case of Forms-Based authentication, it prompts for credentials at workspace creation, but then uses the credentials in the active browser session when opening the workspace. I think this could only be related to your problem if you are logged in as another user in your browser, and that user has access to some, but not all, of the site your workspace connects to.
23 พฤษภาคม 2555 16:03
No apologies needed, points 1 - 5 are spot on with just one more additional point 6, if I click sync I get the 'The parameter is incorrect' groove.exe error described in my first post.
From your bullet list of remote access complications I would say that the the first point might have taken place. What it's saying is that an image was taken from a server where during installation someone (the admin doing the install) launched workspace, took the image then used that image to install on another computer, am I correct?
The server 2008 R2 in question is actually 1 of 4 used to run citrix xenapp at our company and when testing using one of the citrix consoles I got the error so then remoted to the servers directly and got the same error. Another thing that is happening is that if I log off the server after creating the workspace account then log on again a workspace box always pops up (titled workspace configuration wizard) asking if I want to open an existing account or create a new account, I click existing account because I have one saved from my desktop, but it also errors and does not show the site I previously was trying to connect to.
Your bullet points above are a big help, I will forward the info to the system administrators and see what they have to say because from the info you've listed I don't think we will ever be able to run workspace through citrix due to bullet points 2 and 3 above.
Let me know if you have any more info, thanks for the insights so far.
23 พฤษภาคม 2555 17:54
Yes, that's right. When SharePoint Workspace is first launched, it creates configuration items that should be unique to the user. When these items are identical for multiple users, that causes problems.
The lack of a local profile accounts for the account and workspaces that you previously created not being available. For details, see this article: You are prompted to create a new account every time that you start SharePoint Workspace 2010 or Groove 2007
27 มิถุนายน 2555 12:55In our case the timezone was not correct selected after install of all our clients with the sysprep method. Selecting the correct timezone (again) solved our problem.
- เสนอเป็นคำตอบโดย helpdeskslo 28 มิถุนายน 2555 13:39
- ยกเลิกการนำเสนอเป็นคำตอบโดย Hemendra AgrawalMicrosoft Community Contributor, Moderator 1 กุมภาพันธ์ 2556 8:27
28 มิถุนายน 2555 13:58
Thanks for your input, however I can't see how this relates to our citrix xenapp servers where the problem is happening, not on the client.
29 มิถุนายน 2555 10:50
You are right, but we got the same parameter error NUMBER mentioned in our warnings. It tells us that a parameter is incorrect. In our case we found a discrepancy between the timezone that was showed and the one that was selected. Lining them up did the job. It is possible that one error message can have multiple solutions when the parameter list has more than 1 parameter in the call. If MS doesn't mention which of the parameters is wrong users can find a solution for their problem that doesn't have to be a solution for another user. Therefore I put our solution here in the hope other user can try it in their situation.
29 มิถุนายน 2555 11:08
Thanks for clearing that up I now see the connection. My sharepoint involvement has come to an end as this is my last day at current job (back to c# asp.net sql server dev). I've sent the link for this thread to sys admins who'll be taking over so they might be posting in future.