Category Archives: SharePoint 2010

CoolWriteups SharePoint 2010 Post

SharePoint 2010 How To Change The Farm Password

  • Stop the User Profile Synchronization Service running on the Application Server
  • Open Central Administration and navigate to Security > Configure Managed Accounts
  • Click the Edit button in line with the Farm account
  • Check the Change password now checkbox and enter a new password. Remember to make a note of this password and click ok.

    If you receive an ‘Access is Denied’ error, log into the Active Directory Server, right click the Farm account username and bring up the properties. Click the Account tab and ensure that the ‘User Cannot Change Password’ checkbox is unchecked.

  • Once this is done, you will need to update the password for the Forefront Identity Manager Service and Forefront Identity Manager Synchronization Service under Services on the Application Server.
  • Make sure the Farm account is added to the Administrator’s group on the Application server and start the User Profile Synchronization Service under System Settings > Manager Services on Server.
  • Once the service is running, reboot the Web Front End and Application Servers.
CoolWriteups SharePoint 2010 Post

SharePoint 2010 – An error occurred during the “Generate Key” process. Please try again or contact your administrator

Scenario:

In SharePoint 2010, when you try to set up the Secure Store Service Application, one of the first steps is to generate a key. You open up the page under Central Administration > Application Management > Manage Service Applications > Secure Store Service to add a passphrase but see the error message “An error occurred during the “Generate Key” process. Please try again or contact your administrator”.

Looking at the ULS logs you may see this:

“7557 Critical The Secure Store Service application Secure Store Service is not accessible. The full exception text is: User does not have permission to perform the operation.”

Solution:

This could be due to the user account that is logged in to the Central Administration page not having enough permissions to generate the key.

Try using the Farm account.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 – Users Cannot See Publishing Images

Scenario: You’ve just changed the logo on your SharePoint 2010 Intranet site but you as an Administrator or Site Collection owner are the only one who can see it? You’re users see a red cross?

Reason: When you add any image or file to the Site Images document library, the item is saved as a Draft version. Your end users cannot see Draft versions unless you give them access.

Solution:

Go to your Site Images (Publishing Images) folder under All Site Content and:

  • Go to Library Settings > Versioning settings
  • Under Content Approval, select ‘No’ for Require content approval for submitted items?
  • Under Document Version History, select ‘No Versioning’
  • Under Require Check out, select ‘No’ for ‘Require documents to be checked out before they can be edited?’
CoolWriteups SharePoint 2010 Post

SharePoint – Access Denied For User With Full Control When Creating a List Template

Scenario: The user has Full Control to a SharePoint Document Library, however when the user tries to create a list template they see an Access Denied error, similar to the one below.

SharePoint 2010 Access Denied

This could be related to MOSS 2007 or SharePoint 2010 and maybe SharePoint 2013 too.

Solution: User needs Design rights on the List Template Gallery found under Site Settings > List Template Gallery.

  • Create new Permission level with ‘Manage Lists’ and ‘View Items’ options checked under ‘List Permissions’. Also, check the ‘View Pages’ and ‘Open’ permissions under ‘Site Permissions’.
  • Go back to Site Settings > Site Permissions and create a new custom group. Leave the group empty.
  • Go back to the Site/List Template Gallery > library permissions and click ‘Grant Permissions’. Bring up the directory window and type the name of the custom group you created in the previous step.
  • Select the ‘Grant users permissions directly’ radio button and check the new Permission level created above.
CoolWriteups SharePoint 2010 Post

SharePoint 2010 Services Stuck at Stopping or Starting

You log into Central Administration for SharePoint 2010 > System Settings > Services on Server and notice some of the services are stuck at ‘Starting’ or ‘Stopped’.

This could be due to the fact that SharePoint 2010 Administration Service (spadminv4) is not running on the Server. But when you try to start the service, it does not start in a timely fashion. To learn how to start the SPAdminV4 service follow this article: SharePoint 2010 Administration Service Not Starting

1. To solve the ‘Starting’ and ‘Stopping’, log into the server running Central Admin with the Farm account. Ensure the Farm account is a member of the Administrator’s group on the server you are logging in to;

2. Open a Powershell command window and Run as Administrator;

3. To get all the services running on a particular server, run the following command ‘Get-SPServiceInstance –Server ‘servername’. This will bring up a list of services running on the server like below.

4. To stop the service, enter the following command ‘Stop-SPServiceInstance’ and the GUID of the services from the screen above.

5. The status will now change from ‘Starting’ to ‘Stopping’. This will however not complete if the SharePoint 2010 Administration service is still not running. To stop it, run ‘Start-SPAdminJob’. Refer to this article for more info: http://technet.microsoft.com/en-us/library/ee513051%28v=office.14%29.aspx

6. Give it 10 seconds and the service should now be either ‘Stopped’.

7. The ‘Stop-SPServiceInstance’ command can be used to stop a Provisioned service too. A provisionsed service will have a status of ‘Starting’ or ‘Started’.

8. If the service status is ‘Unprovisionsed’, it means the service is ‘Stopped’ or ‘Stopping’.

9. To start a service, use ‘Start-SPServiceInstance’

That’s it.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 – How To Install A Cummulative Patch

Installing a SharePoint 2010 cummulative patch can be tricky. To ensure everything goes smoothly, the following steps will help. Make sure you test this out in your DEV environment first.

Requirements:

1. Farm username and password;
2. Server names;
3. Downloaded patch/update for SharePoint Server 2010 or Foundation 2010;

Steps to install the patch/update:

1. Run the downloaded patch on all the servers in the farm individually starting first with the Application Server, then the Web Front End. The patch is usually an exe file;
2. Reboot the servers;
3. Log back into the Application server or the server that hosts Central Admin and open a Powershell window as an Administrator;
4. First check if an upgrade of the server is needed by entering this command ‘(get-spserver $env:computername).NeedsUpgrade‘. If one is required, enter the following command and run ‘PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures‘. Do this on all the servers in the farm that have SharePoint installed. This will ensure that all the servers in the SharePoint 2010 farm are upgraded and that they all have the same patch status
5. Once this is done, reboot all the servers one by one.
6. Open Services and check to make sure all the SharePoint services are running including SharePoint 2010 Administration. Also, ensure the Forefront services are running on the Application Server;
7. You may notice the databases are now running in compatibility range. To solve the issue run this Powershell command ‘Get-SPContentDatabase –Identity DatabaseName | Upgrade-SPContentDatabase‘. For a non-content database run this command ‘Get-SPDatabase –Identity DatabaseName | Upgrade-SPDatabase’.

That’s it.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 Administration Service SPAdminv4 Not Starting

The SPAdminv4 service fails to start on a server running Windows Server 2008 after you have installed a SharePoint 2010 cummulative patch or are in the process of building a new server farm. This could be a problem on the Web Front End or the Application Server.

The fix is to add a new registry setting.

1. Click Run and enter ‘Regedit’;
2. In the Registry Window, navigate to ‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control’;
3. Right click and create a new DWORD Value option;
4. Replace ‘New Value #1’ with ‘ServicesPipeTimeout’;
5. Right click the new option and click Modify;
6. Enter 60000 as the value and exit the Registry.
7. Restart the server;

The SharePoint 2010 Administration service should now be running.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 Starting, Stopping and Removing a Service or Service Application

Are you having trouble starting, stopping and removing a Service or Service Application? Well take a look at some of the nifty commands below that may help.

To find out what Service Applications are present on the SharePoint 2010 Farm, in a Powershell window (Run as Administrator), enter the following:

1. ‘Get-Help Get-‘ – This will return all the commands that start with a ‘Get-‘;
2. Get-SPEnterpriseSearchServiceInstance is the one you want to use if you’re having trouble with Search. This will list the service instance on each server in the Farm and whether it has the Search service provisioned or not;
3. Stop-SPEnterpriseSearchServiceInstance –ID will stop the service, use this in conjunction with Get-SPEnterpriseSearchServiceInstance.
4. Get-SPServiceInstance will list all the Services running on a Server;
5. Get-SPDatabase will display a list of SharePoint Databases;
6. Start-SPServiceInstance -ID will start a Service. Refer to this link for more: http://technet.microsoft.com/en-us/library/ee704549%28v=office.14%29.aspx;
7. Remove-SPServiceApplication -Id -RemoveData will remove a Service Application along with it’s data. Refer to this link for more: http://technet.microsoft.com/en-us/library/ee806875%28v=office.14%29.aspx;
8. Use -Local for services running on the Server you are logged in to.

That’s it. Enjoy

Derek Halstead

CoolWriteups SharePoint 2010 Post

SharePoint 2010 – Delete Search Service Application

Ran into a sticky situation where I had to delete a corrupt Search Service Application in SharePoint 2010.

To do this make sure your Farm account is:

1. Used to run the SharePoint Timer Service;
2. Is a member of the local Administrator group on the Web Front End and Application Server;
3. Make sure the Timer service and other SharePoint services are running.

You could try and delete the Search Service Application via Central Administration by selecting the Service Application and clicking the Delete option in the ribbon above.

SharePoint 2010 - Delete Search Service ApplicationIf that doesn’t work, you could try this option:

1. Open Powershell, run as Administrator;
2. Run this command – Get-SPServiceApplication. This will give you a list of the Service Applications on the Farm including the corrupt Search Service Application to delete;
3. Make a note of the GUID connected to the Service Application;
4. Then run Remove-SPServiceApplication -Id “replace with Guid” -removedata

Refer to this article for more info: http://technet.microsoft.com/en-us/library/ee806875%28v=office.14%29.aspx

If the above Powershell command doesn’t do the trick, you could resort to STSADM commands as a last resort.

1. Get the GUID of the Search Service Application above by running the same command above using a Powershell command window (Run as Administrator);
2. The run stsadm -o deleteconfigurationobject -id “replace with GUID”;

Keep checking the log files, you could be missing a PropertyStore database or one of the other SharePoint databases. If this is true then restore the database and continue to the steps above.

That’s it, good luck with it.

Derek Halstead

CoolWriteups SharePoint 2010 Post

Solved: SharePoint 2010 – No Connectivity With The Server

No Connectivity With Server

If you see the error above, the solution below worked for me:

  • Although this should have been done as a group policy, it wasnt. You will need to change the security in your Intranet Zone under the IE browser’s Security tab.
  • Go To IE > Tools > Options > Security tab;
  • Under the Security tab, pick ‘Local Intranet’;
  • Click Custom Level and in the next window scroll all the way to th bottom of that window and pick ‘Automatic logon with current user name and password.’ This will also stop the browser prompting for your credentials.

Any questions let us know below.

SharePoint 2010 Cascading Dropdownlists

For this example, download the attached Word document for screenshots and code.

Lists
a. Ideas;
b. Options;
c. Benefits Realisation.

JQuery
a. jquery-1.3.2.min.js;
b. jquery.SPServices-0.7.1a.min.js

Code and Screenshots

Click here: SharePoint 2010 Cascading Lists Screenshots

Other Resources

Credit goes to SharePoint Kings

Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.

CoolWriteups SharePoint 2010 Post

CoolWriteups.com Solved: SharePoint 2010 Solution Stuck At Deploying

Hello and welcome to CoolWriteups.com.

SharePoint 2010 Deploying Solution Stuck ErrorAre you trying to deploy a SharePoint 2010 Solution file (.wsp) only to notice the Status is stuck at “Deploying(scheduled at 01/01/2012 11:00 AM)?

If the SharePoint 2010 Farm is made up of multiple front end servers (WFEs) chances are the deployment is in queue to be deployed at one of the front end servers.

Deploying WSP Solution CommandTo deploy the solutions file:

  • Open a Command Prompt (Start > Run > cmd) and type in “%commonprogramfiles%\microsoft shared\web server extensions\14\bin”;
  • Then type the following command “stsadm -o ExecAdmSvcJobs” on all front end servers (one by one) including the Application server where you tried to add the solution. Then refresh the Farm Solutions page after approx 5 seconds.

Alternatively, if your Farm is made up of just the one server then restart the Timer service and then try and deploy the solution.

Questions, comments always welcome.

Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.

InfoPath 2010 Logo

InfoPath Forms Services Support Hidden Feature Not Activated

InfoPath Forms Services Support Hidden Feature Not Activated

When you log into your SharePoint site, open a Form Library and click New to create a new InfoPath form item, you may see the error message “Activation could not be completed because the InfoPath Forms Services support feature is not present.”
This is a hidden feature and one that does not appear in the Central Administration user inferface.

Some forums out there suggest running the following stsadm commands:

  • STSADM.EXE -o deactivatefeature -filename IPFSSiteFeatures\feature.xml -force -url %SITE_COLLECTION_URL%
  • STSADM.EXE -o deactivatefeature -filename IPFSWebFeatures\feature.xml -force -url %SITE_COLLECTION_URL%
  • STSADM.EXE -o activatefeature -filename IPFSSiteFeatures\feature.xml -url %Sitecollection_URL% -force
  • STSADM.EXE -o activatefeature -filename IPFSWebFeatures\feature.xml -url %sitecollection_URL% -force

In general, you don’t need to run the commands above as the InfoPath Forms Services support feature is a hidden feature and is present by default unless someone turns them off manually.

For me, the solution was to turn on a different feature found at the Site Collection level called “Open Documents in Client Applications by Default” which can be found under Site Actions > Site Settings > Modify All Settings > Site Collection Features. Turning this feature ON opened the InfoPath forms in the InfoPath Filler program which is standard across the organisation.

So, if the above STSADM commands don’t do it for you, try turning on the “Open Documents in Client Applications by Default” feature.

Questions, comments welcome.

Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 Upgrade – Checklist

Welcome to CoolWriteups. Below I have put together a set a activities to check to ensure a smooth upgrade of your MOSS 2007 environment to SharePoint 2010.

Before the upgrade

  • If you have a Nintex database to upgrade, ensure you have first updated the 2007 Nintex database to the latest version (2.0.1.5 at the time of writing this) in your existing 2007 environment or move it to a Test 2007 environment and update it there. Then install Nintex Workflow 2010 software on your new 2010 Production Server, update it to the latest version (2.3.5.0 at the time of writing this) if you have to. To find out the version of Nintex, check the Licensing page under Nintex Workflow Management. Then restore the updated 2007 Nintex database in the 2010 environment and attach it to Nintex Workflow 2010 by using the Database Setup page found under Nintex Workflow Management;
  • Before starting the actual upgrade, ensure that all the content databases are restored to the new 2010 Production Database Server and all accounts have been recreated ensuring that the FARM account has DBOwner rights on the content databases;
  • Make sure you have enough disk space allocated to the drive where the content databases reside. For example a 350GB content database will grow by approximately 10GB. I know what you’re thinking, so 360GB would be fine? I would recommend the drive be 500GB just to be on the safe side;
  • Also, ensure that the log file is set to autogrow and that no maximum limit is set on it’s size in the Database properties window in SQL Server Management Studio. If your log files are stored on a different drive make sure the drive is more than 150GB in size, your 350GB content database’s log file is likely to grow to approximately 150GB so make sure you have allocated atleast 200GB to the drive. More is better.

During the Upgrade

  • Log into your Production Application Server with the FARM account and open a Powershell command prompt. Type in the following command: Mount-SPContentDatabase -Name -DatabaseServer -WebApplication [-Updateuserexperience], where:

    databasename‘ is the name of the database you want to upgrade.

    servername‘ is server on which the database is stored.

    url‘ is the URL for the Web application that will host the sites.

    Updateuserexperience is the choice to update to the new user experience or stay in the old user experience (part of Visual Upgrade). When you include this parameter, the site is set to preview the new user experience. Omit this parameter if you want the site to remain in the old user experience after upgrade. For more information, see Plan visual upgrade (SharePoint Server 2010). Refer to this link for more details: http://technet.microsoft.com/en-us/library/cc263299.aspx#AddDB

  • Once you run the command, you can keep track of the upgrade by opening the Central Administration page then > Upgrade and Migration > Check Upgrade Status;
  • You can also start Task Manager on the SharePoint 2010 Application server, click the ‘Networking’ tab to see if there is any traffic going through to the Database Server.
  • Most important is the Upgrade log file which can be found in the 14 Hive in the Logs folder or if you have your log files stored in a different drive then check there. The Upgrade log file will give you information about the start time of the upgrade, what it has done, what features are missing, errors, warnings etc;
  • Other options to check the progress of the upgrade include Opening SQL Server Management Studio then right click the Server Instance and select Activity Monitor to make note of the processes running against the content database that is being upgraded to SharePoint 2010. Keep an eye out for any locks;
  • You can also open a new Query Window in SQL Server Management Studio against the content database and enter the following query: SP_HELPDB ‘DBName’ which will give you a list of properties along with information about the log file, the size etc. This is important as most upgrades fail due to a lack of disk space allocated or the log file is set to have a maximum limit that is less that what it needs;
  • During the upgrade the SQL Server will record any errors which can be found by clicking SQL Server Agent in SQL Server Management Studio, then click the Error Logs folder, select SQL Server as the option (not SQL Server Agent) and then double click the ‘Current’ log file. This will tell you if there are any errors and what caused the error.

Questions and Comments always welcome.

Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.

OneNote 2010

OneNote 2010 with SharePoint 2010 Example

In this article I am going to share with you the benefits of OneNote 2010 and how you can leverage it’s features to get rid of all your office documentation stored in different sources and centralise all that information in an electronic notebook.

What is OneNote? OneNote is a digital notebook that let’s you manage your information, orgainise it, quickly find it, and share it with others.

Below is a graphical representation of what OneNote can do for you at home, school and at work.
What is OneNote?

OneNote at Work

OneNote At School

OneNote At Home

OneNote works on the same idea of a notebook. Items in OneNote are stored on pages, these pages can be of any size unlike the pages in a normal notebook and there is no limit to the number of pages you can create. Just like in a normal notebook, you can use sections (represented by Tabs at the top of the page) to organise pages inside a OneNote notebook. You can also rename a section or add more to the OneNote notebook.

There is also a special section called Unfiled Notes which can be used to store random notes. You can move these random notes to anywhere in your OneNote notebook once you have decided where to put them.

To demonstrate the use of OneNote I am going to show you how I have planned my next holiday to America using OneNote. I will then show you how easy it is to share this information with collegues and friends using SharePoint 2010.

To begin, my trip to the US needs the following:

  • A flight ticket, a Visa and Passport which I will store in a section called “Travel Documents”;
  • I will also need a list of contacts in the US who include family and friends. I will store this information in a section called “Contacts”;
  • A list of places I would like to visit which I will store in a section called “Places to Visit”;
  • I’m pretty sure I will keep track of all my receipts along the way, with OneNote it is easy to scan and print a receipt directly to your OneNote notebook instead of printing it to a sheet of paper. I will store these printed receipts in a section called “Receipts”
  • Remember, all the information stored in a OneNote notebook can be shared with friends and collegues. You can do this by syncing your notebook with SharePoint 2010 and then giving only certain people access to the notebook.

Ok, so lets start this exercise by first creating a Document Library in SharePoint 2010 and then creating a OneNote notebook.

  • Log into your SharePoint 2010 Team site and create a new Document Library, call it “My American Holiday”;
  • Then go to Start > All Programs > Microsoft Office > OneNote 2010, to open OneNote. Click File > New, to create a new notebook. In the screen, add a name for the notebook, I have called mine “My American Holiday”;
  • I then selected the Network Location option as I plan on syncing my notebook with SharePoint to share with my collegues and friends;
  • CoolWriteups.com - Create OneNote Notebook

  • Once the notebook is created, you should see a Microsoft OneNote message box saying the notebook has been created and is accessible to anyone. You can choose to email the link to a friend or a collegue using Outlook 2010.
  • CoolWriteups.com - Notebook Created

  • The first section of the notebook created by default is called “New Section 1”. Right click the section and select “Rename” to rename it to “Travel Documents”. In the same way, go ahead and add three more sections and name them “Contacts”, “Places to Visit” and “Receipts”. Your notebook should look like the one below.;
  • CoolWriteups.com OneNote 2010 - Sections

  • Now start adding content to the sections created above as you would normally do using a normal notebook. Click save as you go and the information is automatically saved to the SharePoint Document Library as seen below.
  • Coolwriteups.com - SharePoint OneNote Notebook

As you can see above, the possibilities are endless. Students can use OneNote to keep track of individual projects, real estate agents can use it to keep track of potential buyers, the properties they are interested in and other contact details. Large organisations can use it to keep track of various in-house projects and share all documentation with other staff across the organisation centralling using the Intranet.

I hope you found this post useful, questions and comments always welcome. Cheers.

Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.

CoolWriteups SharePoint 2010 Post

SharePoint 2010 Upgrade: Steps To Upgrade InfoPath Forms From MOSS 2007 To SharePoint 2010

In this post I have put together the steps needed to upgrade InfoPath forms from MOSS 2007 to SharePoint 2010 below. Please note these steps are at a very high level but it will point you in the right direction. There are several resources out there and most notably this link helps the most: http://technet.microsoft.com/en-us/library/ee704551.aspx

This is what I did to upgrade InfoPath forms as part of the SharePoint 2010 Upgrade.

  • Log into the MOSS 2007 Production server, open the STSADM command from C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin
  • Run the following command: stsadm -o exportipfsadminobjects -filename “C:\AdminApprovedInfoPathForms\AAIPF.cab”. This will export any Administrator approved InfoPath Data Connections and Templates. It is important that you do this step first before starting the actual upgrade process.
  • Next, you will need to import this into the SharePoint 2010 Application Server. Log into the server and open a Powershell Command Window. Enter the following command: Import-SPInfoPathAdministrationFiles -path “C:\InfoPathFiles\AAIPF.cab”. The InfoPathFiles folder is a holding folder on the 2010 server.
  • Now start the upgrade of the content databases using the Mount-SPContentDatabase command, refer to this: http://technet.microsoft.com/en-us/library/ff607581.aspx
  • Once all the content databases have been attached and the upgrade completes successfully, it is important that you change all User created Data Connection files (.udcx) and Form Templates (.xsn) to redirect to the new server. To do this run the following command: Update-SPInfoPathUserFileUrl -WebApplication “http://coolwriteups2010” – find “http://coolwriteups2007” –replace “http://coolwriteups2010”. Refer to this article: http://technet.microsoft.com/en-us/library/ff607651.aspx
  • To redirect any Administrator approved Data Connections or Templates run this command: Update-SPInfoPathAdminFileUrl -WebApplication “http://coolwriteups2010” –find “http://contoso2007” –replace “http://contoso2010”. Refer to this article: http://technet.microsoft.com/en-us/library/ff607606.aspx
  • While the Update-SPInfoPathUserFileUrl and Update-SPInfoPathAdminFileUrl commands are running, it helps if you open Central Administration and navigate to Monitoring > Check Job Status. Keep an eye on the Running Jobs section, check the “Form Library URL Repair” job and ensure that is completes successfully. If the job fails, click the “Failed” link which could display an error message along the lines: “‘Content-Type’ is an unexpected token. The expected token is ‘”‘ or ”’. Line 6, position 18″. The Job History page will also display the name of the Content Database the command failed to run.
  • **Update 08 August 2012: I have found a solution to the problem, you can run the Update-SPInfoPathUserFile Powershell command by targeting a Site, Web Application or a Content Database. If the option to use the Web Application does not work, try using a particular Site or the Content database on which it fails to run.

    Also, you may notice after running the command, although the Data Connections have now been updated to point to the new server, if you were to open the form up in Design View it could still say it is Publishing to the old server (check status bar to the right in InfoPath Designer 2010).

    To solve this problem, you will need to republish the form by pointing it to the new SharePoint 2010 address (http://coolwriteups2010).

  • **Update 20 August 2012: The above message was related to an ODC connection file in a Data Connection Library which by default has two content types. The Update-SPInfoPathUserFileUrl is unable to update this ODC connection file and therefore stops editing the XSN and UDCX files. The solution is to delete the Data Connection Library along with any connection files present, from the site as well as from the Recycle Bin.
  • Update-SPInfoPathUserFileUrl Powershell Command

  • Other things to check, SharePoint sites will most likely contain multiple Data Connection Libraries. Open the library in Windows Explorer view, right click a connection file and open in your favourite editor. Change any reference to the old server and replace with the new server. For example: Change http://coolwriteups2007/sites to http://coolwriteups2010/sites.

Questions & comments always welcome, so let me know what you think.

Cheers

Join the Forum discussion on this post

Send us a quick enquiry at Certified Solutions Australia to find out how we can help you.

CoolWriteups SharePoint 2010 Post

CoolWriteups Solved : Muhimbi The remote Server Returned An Error: (401) Unauthorized

Problem:

The service account that MDCS is running under does not have the privileges to load the XSN file from SharePoint

Error:

07/31/2012 08:52:17.58 w3wp.exe (0x1A28) 0x1E18 SharePoint Foundation Workflow Infrastructure 98d4 Unexpected System.ServiceModel.FaultException`1[SomeCompany.ConvertToPdf.WorkflowActivity.MuhimbiService.WebServiceFaultException]: Muhimbi.DocumentConverter.WebService.Data.WebServiceInternalException: Exception of type ‘Muhimbi.DocumentConverter.WebService.Data.WebServiceInternalException’ was thrown. – Details: “The remote server returned an error: (401) Unauthorized.” at Muhimbi.DocumentConverter.WebService.InfoPathConverterFullFidelity.Convert() at Muhimbi.DocumentConverter.WebService.DocumentConverterService.Convert(Byte[] sourceFile, OpenOptions openOptions, ConversionSettings conversionSettings, Boolean checkLicenseStatus) (Fault Detail is equal to SomeCompany.ConvertToPdf.WorkflowActivity.MuhimbiService.WebServiceFaultException). 3c893397-76f0-40ed-af08-5e4023277759

Solution:

  • Log into the Server running the Muhimbi Document Converter Service with an account that has sufficient privileges to access the Services running on the server;
  • Go to Start > Administrative Tools > Services and scroll down till you find “Muhimbi Document Converter Service”;
  • Right click the service and open Properties, click the Log On Tab and make a note of the account running the service;
  • Go back to the SharePoint 2010 site, click Site Actions > Site Permissions and add the Service Account to the “Visitors” group.

Helpful Resources:

Questions and comments welcome, leave a message below.

Thank you.

Join the Forum discussion on this post