LinkReplaceTimerJob threw an exception after running Update-SPInfoPathUserFileUrl

* A .rsds file is a shared data source file published to SharePoint by users to allow SQL reports to run properly in SSRS integrated mode with SharePoint. Often, customers deploy the shared data source file to a Data Connection library since the file defines a data connection to a data source.

Reference: http://msdn.microsoft.com/en-us/library/bb326288.aspx

* Publish a shared Data source file to a data connection library (or simply upload an existing .rsds file if you don't have SSRS running)
-
* Run the following PowerShell command:
Get-SPWebApplication http://sp2010 | Update-SPInfoPathUserFileUrl -find "http://sp2007" -replace "http://sp2010"

* From the event viewer on the server, you will see the following error:

"The Execute method of job definition Microsoft.SharePoint.Utilities.LinkReplaceTimerJob threw an exception. Object reference not set to an instance of an object."
Below is what I have gathered from Reflector and ULS logs:
• From Microsoft.SharePoint.Utilities.SharePointLinkReplace

o SharePoint will call FixList on all the lists

o If the list is a Data connection library, call FixUDCFileon every file if the file is not .aspx

o FixUDCFile will process the file (ULS log: "Processing data connection file" was called before exception was thrown), then call FixUdcXML and then FixXML, which will then callPerformChecksOnXMLDocument

o Once in PerformChecksOnXMLDocument, because the .rsds file has a different xml structure than both XSN and UDCX files, the code looks for nodes that cannot be found, hence resulting in an Object reference not set to an instance of an object exception.

Resolution:

• Before running the PowerShell command, remove or rename the .rsds file to aspx so that the timer job will skip processing rsds files

Comments

Post a Comment

Popular posts from this blog

"There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word." Office WebApp Error

Problem: When Opening a word document I get the following error when Office Web Apps tries to render the document " There's a configuration problem preventing us from getting your document. If possible, try opening this document in Microsoft Word. " Initial Hypothesis: Check the ULS logs on the Web Front End (SharePoint Server) as this doesn't tell me much.  I found the following issue in my UL S: WOPI (CheckFile) - Invalid Proof Signature for file SandPit Environment Setup.docx url: http://web-sp2013-uat.demo.dev/Docs/_vti_bin/wopi.ashx/files/6d0f38c0d5554c87a655558da9cedcad?access_token... Resolution: Run the following PS> Update-SPWOPIProofKey -ServerName "wca-uat.demo.dev" More Info: http://technet.microsoft.com/en-us/library/jj219460.aspx
Continue Read

"We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Excel Service SharePoint

Image
This article explains about Excel related issue in our SharePoint 2013 Environment. Whenever user tries to open excel files uploaded in document library, it launches browser to open the file and then displays below error- " We’re sorry. We ran into a problem completing your request. Please try that again in few minutes." Also see below screenshot- As part of issue analysis, following checks were performed- 1.) Check if Excel Services is running. ( This was running in our case. ) Open Central Administration -> System Settings -> Manage Services on Server -> Excel Calculation Service -> Started 2.) Check if Excel Service Application is associated to Web Application in question. ( This was configured in our case. ) Open Central Administration -> Application Management -> Manage Web Applications -> Select Web Application -> Select Configure Service Associations 3.) Check if Trusted File Location is configured for Excel Service...
Continue Read

Deployment error "The web.config is invalid on this IIS Web Site"

I've developed a webpart that deploys and works properly in my DEV environment. When I attempt to deploy to PROD I get the following error: SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER : http://acme.com/ : SharePoint - 41981 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\41981\web.config. SOMESERVER1 : http://acme.com/ : SharePoint - 23994 : Error: The web.config is invalid on this IIS Web Site: C:\Inetpub\wwwroot\wss\VirtualDirectories\23994\web.config. None of these virtual directories exist. Any ideas how to resolve? Solution : In Central Administration-> Operation-> Services on Server, please stop the Windows SharePoint Services Web Application service , SharePoint will remove the sites in IIS. And then start the Windows SharePoint Services Web Application service agai...
Continue Read