SharePoint – Agile BI http://agilebi.com A community for sharing ideas about business intelligence development using agile methods. Sat, 14 Jan 2012 01:52:33 +0000 en-US hourly 1 https://wordpress.org/?v=6.2.2 SharePoint JavaScript Error: Library Not Registered http://agilebi.com/blog/2010/01/05/sharepoint-javascript-error-library-not-registered/ Tue, 05 Jan 2010 07:32:00 +0000 http://7.16 Continue reading →]]> The other day one of my clients upgraded from Outlook 2003 to Outlook 2007.  Since then, whenever she went to her company’s SharePoint site, she received the following error: 

================================================================== 

Website error details 

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; 
.NET CLR 1.1.4322; MS-RTC LM 8; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Timestamp: Mon, 4 Jan 2010 18:27:45 UTC

Message: Library not registered.

Line: 1935
Char: 4
Code: 0
URL: http://server/_layouts/1033/init.js?rev=ck%2BHdHQ8ABQHif7kr%2Bj7iQ%3D%3D

==================================================================

Apparently the Outlook upgrade did something to a DLL (removed it?) that SharePoint needs.
If you have just upgraded from Outlook 2003 to Outlook 2007 and you receive a similar error, simply run Office Diagnostics and it should fix the problem!

To run Office Diagnostics follow these steps:
1. Open Microsoft Outlook 2007
2. On the Help menu, click Office Diagnostics
3. Click Continue, and then click Start Diagnostics

]]> The Path Specified Cannot Be Used At This Time http://agilebi.com/blog/2009/08/03/the-path-specified-cannot-be-used-at-this-time/ Mon, 03 Aug 2009 07:43:00 +0000 http://7.13 Continue reading →]]>

This morning I needed to check the properties for one of our SharePoint application pools so I logged onto the server and opened Internet Information Services (IIS) Manager.  To my surprize the root was empty; it should have automatically connected to the localhost.  To my even greater surprize, all attempts to manually get IIS to connect to the server yeilded the message “The path specified cannot be used at this time”. 


After a quick search I found a post by Old Nick stating that this problem is easily resolved by restarting the Windows SharePoint Services Timer service.  That’s pretty obvious, right?  Sure enough, restarting that service solved the problem.  The next time I opened IIS it connected to the localhost. 

]]>