Internet Explorer Script Error Library Not Registered Sharepoint
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server BizTalk Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Error: "Library not registered" in IE Internet Explorer Development > Internet Explorer Web Development Question 0 Sign in to vote Hi, When i am browing a site in IE7, getting an script error "Library not registered". Please help me in understanding possible cause of this error. Thank you Monday, November 07, 2011 10:46 AM Reply | Quote Answers 0 Sign in to vote Hi Srinivasu, Please try to check out the resolution to solve this problem: http://support.microsoft.com/kb/q274038/ hope this helps, thanks.Please mark the replies as answers if they help or unmark if not. If you have any feedback about my replies, please contact msdnmg@microsoft.com Microsoft One Code Framework Mark
on January 5, 2010 by Melinda Cole 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: https://social.msdn.microsoft.com/Forums/ie/en-US/c0f3f376-4722-4df8-9948-a8211cf8b1ca/error-library-not-registered-in-ie?forum=iewebdevelopment 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 http://agilebi.com/mcole/2010/01/05/sharepoint-javascript-error-library-not-registered/ Outlook 2007 2. On the Help menu, click Office Diagnostics 3. Click Continue, and then click Start Diagnostics This entry was posted in SharePoint and tagged DLL, JavaScript, Library Not Registered, MOSS, Office Diagnostics, Outlook, SharePoint. Bookmark the permalink. ← Adding Custom Components to SSIS SQL Server 2005 Installation Failures → 15 Responses to SharePoint JavaScript Error: Library Not Registered http:// says: April 15, 2010 at 8:14 am I had lots of bugs using share point, so no comment here… Reply Darcy says: November 12, 2010 at 6:10 pm This was the solution to my issue with that stupid error keeping me from working with my sharepoint site. I inherrited a laptop from someone and had no idea an "upgrade" was performed. Thanks for this-SUPER HELPFUL!! Reply mcole says: November 21, 2010 at 6:19 pm Glad it helped you out! Reply ptllogic says: December 3, 2010 at 12:16 pm Hi, It worked for me as well!!! - thanks! -Regds Reply Tom Molskow says: December 28, 2010 at 9:05 pm Excel
x64 & SharePoint 2007So I’ve been running Office 2010 x64 for quite some time now — through alpha, beta and the RC. Now, I’m waiting for http://jpd.ms/init-js-library-not-registered-office-2010-x64-sharepoint-2007/ RC with the hopes that this has been fixed.Seems there’s a little something wrong with the Name ActiveX Control that SharePoint uses for OCS presence info. Whenever I run any SharePoint site, I get stuck with a bunch of JavaScript errors, which in turn break other scripts, leading to a less-than-optimal experience.Does this look internet explorer familiar?Debugging the page gives a bit more insight, but not much:So we know it’s the IM Presence Control — (on a side note, this is why internet-facing SharePoint sites you may come ask you to run ‘Name ActiveX Control’).I did some fishing through the IE Add-ons, only to realize that the NameCtrl is missing — then it hit me…The internet explorer script ProblemI’m running Windows 7 x64, and the x64 Office 2010 clients. Where does this lead us? The x64 version of Internet Explorer.Hit your start menu and type ‘internet explorer 64’ — you should see it pop up in the menu.Fire this up, and browse to your SharePoint site — you’ll notice an error-free interface — no JS errors — meaning any of your additional scripts (like the one we use for navigation) will work properly.So take a look into the Add-Ons in IE x64 — you’ll see the NameCtrl ActiveX control listed in there.Which makes sense, if you think about it — the default IE in Windows x64 is 32-bit IE, ironically to maintain plugin compatibility…64-bit plug-ins aren’t going to work in 32-bit IE, so it all falls into place.But the irony here leaves us with a new problem — do we use IE x64 for everyday use? Or find a 32-bit NameCtrl to install into 32-bit IE?Of course, there’s one other problem — no presence. Even though the NameCtrl gets loaded and is available to the