DLL – Agile BI http://agilebi.com A community for sharing ideas about business intelligence development using agile methods. Sat, 14 Jan 2012 02:00:53 +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

]]> Adding Custom Components to SSIS http://agilebi.com/blog/2009/08/18/adding-custom-components-to-ssis/ Tue, 18 Aug 2009 11:08:00 +0000 http://7.14 Continue reading →]]> Below are the basic steps for adding custom components to SSIS; however, for more in-depth information I highly recommend reading Matthew Roche’s post about deploying and testing custom SSIS components. 

1. Register the custom assembly in the Global Assembly Cache (GAC)

Copy the DLL to the c:windowsassembly directory.  The easiest way is to drag and drop the DLL using Windows Explorer (right clicking on the DLL and doing a copy/paste will not work).  Alternatively you can use the command line utility called GACUTIL.EXE (for more info about GACUTIL see the link above to Matthew’s Roche’s post).  Either way you will need Admin rights. 

2. Copy the custom assembly to Visual Studio’s “special folder” 

Copy the DLL to the appropriate subfolder in the C:Program FilesMicrosoft SQL Server90DTS directory.  For Control Flow Tasks put the custom assembly in the Tasks folder; for Data Flow Tasks use the PipelineComponents folder.  Remember that Visual Studio is a 32 bit application.  If you’re running on a 64 bit machine, make sure to use the Program Files (x86) path, otherwise you won’t see your component listed in the Choose Toolbox Items window of Step 3.

3. Add the component to the SSIS toolbox 

Open an Integration Services project in Visual Studio, right click anywhere in the Toolbox, and select Choose Items.  Go to the appropriate tab in the Choose Toolbox Items window and select the appropriate components.  

]]>