Moving SSIS packages from Development to Production

I built a few packages on my development machine and it worked fine without any major hiccups. Then after moving the packages to the destination server, it started throwing weird errors. I had first changed the connection strings in the package configuration file but still the following errors started showing up :

First Error:

a)Failed to decrypt protected XML node "PackagePassword" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.

b)Failed to decrypt protected XML node "DTS:Property" with error 0x80070002 "The system cannot find the file specified.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available.

This happens because of the package protection level which is by default set to "EncryptWithSensitiveKey". Setting the package protection level to "DontSaveSensitive" helped me to remove these errors. This can be done by right clicking the package in the designer and changing the properties
Also, I setup the proxy sever agent so that the package runs under my account(the one which created the package)

Second Error:

After the first error was resolved, now was the time to run the packages. When I ran the package, it threw an error which was something like this:

SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "*****" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed

The error was happening in an access datasource. I went back into the package configuration file and removed the initial catalog parameter value(which was empty by the way) and voila, it worked.
This post helped me to get through :
https://forums.microsoft.com/msdn/showpost.aspx?postid=73863&siteid=1

Code Camp

Last week I was at Phili Code camp and it was great to be there. There were some really good sessions on Advanced asp.net, Http handlers, and Test driven development. I attended 4 sessions and though it was a code camp, only the first two sessions had something related to code and the rest were more kind of presentations. Other than that I have been pretty busy with my schedule without much time for my own projects. Hopefully, I will post something interesting soon.

PDF ifilter for MOSS 2007

In order to index pdf documents and their content, you need to install an out of box ifilter (ex. Adobe) on the Indexing Server(remember it is the indexing server and not the web front end server). This is what I did :

• I stopped the IIS admin service on the Indexing server and WFE server
• Installed the ifilter on the Indexing server
• Added the icpdf.gif image(pdf icon - search in google for this one) to the WFE server (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images)
• Added the following pdf mapping in the Docicon.xml file (C:\Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\DOCICON.XML)
• Added the pdf file type to SSP -> Search Settings -> File Types
• Did an iisreset(on both the web and index server) and started a full crawl on the required content sources

Initially, I installed it only on the web front end server and though it would crawl the pdf's, it would throw an error like "the file might be corrupted or could not load the item". Later I realised that it needs to be installed on indexing and not web front end server. Hope this helps someone....

MOSS 2007 Search and Basic Authentication

During the weekend, I tried to start a MOSS crawl and during the crawl, the crawler would crawl only specific content and was giving an access denied message for most of the content. It took me sometime to figure out that MOSS crawl wouldn't work with Basic Authentication. I knew that it would work with Windows Authentication, but had no idea about this one. Once I changed it to Windows Authentication, the crawl was working properly. So finally the moral of the story is : Search crawl works only with Windows Authentication and nothing else (not basic and not forms definitely.....)

MOSS Errors in event log

These are the errors, I see everyday....
-------------------------------------------------------------------------------------
Event Type: Error
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 10036
Date: 8/22/2007
Time: 6:23:45 AM
User: N/A
Computer: ApplicationServer
Description:
A database error occurred.

Source: Microsoft OLE DB Provider for SQL Server
Code: 17 occurred 1 time(s)
Description: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

Context: Application '72a8496b-8f45-40e0-9c3b-0bfeb9565e52'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-------------------------------------------------------------------------------------

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: General
Event ID: 27745
Date: 8/22/2007
Time: 6:23:56 AM
User: N/A
Computer: ApplicationServer
Description:
The description for Event ID ( 27745 ) in Source ( Windows SharePoint Services 3 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: #50071: Unable to connect to the database SharePointConfig on sqlserver. Check the database connection information and make sure that the database server is running..

-------------------------------------------------------------------------------------


Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 8/22/2007
Time: 6:41:26 AM
User: N/A
Computer: ApplicationServer
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (0a1fd5de-493b-4cf7-b48e-7920103d4628).

Reason: Object 72a8496b-8f45-40e0-9c3b-0bfeb9565e52 not found.

Techinal Support Details:
System.Collections.Generic.KeyNotFoundException: Object 72a8496b-8f45-40e0-9c3b-0bfeb9565e52 not found.
at Microsoft.Office.Server.Search.Administration.SearchApi.get_App()
at Microsoft.Office.Server.Search.Administration.SearchApi.SetUsersPermittedToQuery(String[] userNames, Boolean force)
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

-------------------------------------------------------------------------------------

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 8/22/2007
Time: 8:18:36 AM
User: N/A
Computer: ApplicationServer
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (0a1fd5de-493b-4cf7-b48e-7920103d4628).

Reason: The trust relationship between this workstation and the primary domain failed. (Exception from HRESULT: 0x800706FD)

Techinal Support Details:
System.Runtime.InteropServices.COMException (0x800706FD): The trust relationship between this workstation and the primary domain failed. (Exception from HRESULT: 0x800706FD)
at Microsoft.Office.Server.Search.Administration.MSSITLB.IGatherApplication2.SetUsersPermittedToQuery(String[] psaAccountNames, Int32 fForce)
at Microsoft.Office.Server.Search.Administration.SearchApi.SetUsersPermittedToQuery(String[] userNames, Boolean force)
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


-------------------------------------------------------------------------------------

Event Type: Error
Event Source: Windows SharePoint Services 3 Search
Event Category: Gatherer
Event ID: 2424
Date: 8/23/2007
Time: 6:45:02 PM
User: N/A
Computer: WebServer
Description:
The update cannot be started because the content sources cannot be accessed. Fix the errors and try the update again.

Context: Application 'Search', Catalog 'index file on the search server Search'

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------------------------------------------

Bourne Ultimatum - First day

I watched the last part of the bourne series today and as the name says, it is really ultimate. In this movie, Jason bourne tries to understand his origin and during the process completely knows about himself in the end. Julia styles is good in her role and so is Joan Allen. The action packed sequences are worth watching a second time. From the beginning to the end, its packed with action giving very little scope for dramatic sequences. Do watch the movie if you like action movie and you won't walk out of the movie hall disappointed. Overall, its an amazing end to the trilogy.

Core Schema Files in WSS 3.0

The following are the core schema files in WSS 3.0 and are really important when customizing the site definitions:

• WebTemp.xml -- Defines the configurations available for creating sites
• Onet.xml -- Defines the top navigation, quick launch areas, specifies which lists are available, specifies the document templates and defines the base types of lists
• Schema.xml -- Defines the forms, views, toolbars and any special fields for a list type

Always create a copy of these files instead of directly editing them. All the customized files are finally merged with the orginal one at runtime.