SSIS Lotus Notes Integration Duct Tape Fix

So, we're switching from a server running SQL Server 2000 to a new server running SQL Server 2008.  I have this DTS package that for six years has been happily pulling data from a Lotus Notes database.  I was able to create an SSIS package that does the same thing, although using a Data Reader for the Lotus Notes data.  When I run the package itself, on the server, via BIDS, it runs fine.  However, running it from a SQL Server Agent job produces this error:

Error: 2010-09-01 12:42:19.83     Code: 0xC0047062     Source: Transfer LN_All_By_Consultant DataReader Source [1]     Description: System.Data.Odbc.OdbcException: ERROR [S1C00] [Lotus][ODBC Lotus Notes]Driver not capable  ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed  ERROR [01000] [Microsoft][ODBC Driver Manager] The driver doesn't support the version of ODBC behavior that the application requested (see SQLSetEnvAttr).  ERROR [S1000] [Lotus][ODBC Lotus Notes]Failed to switch to ID file C:\Program Files\lotus\notes\data\admin.id. Wrong Password. (Passwords are case sensitive - be sure to use correct upper and lower case.)  ERROR [28000] [Lotus][ODBC Lotus Notes]Invalid authorization specification     at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCo...  The package execution fa...  The step failed.

After searching for the answer in vain on the Internet, and hitting my head on the desk for three days, I finally came up with this solution:  I am using an Access database file on the server, linking the three Lotus tables I need via ODBC.  Then I create user queries on the linked tables, and voilà, SSIS is able to access these via OLE DB and I can get my data.
Of course, if anyone out there has the real solution, please let me know!

Crystal Report Viewer 8.0 and IIS 6

Technically, Crystal Web Components 8.0 aren't supported on Windows Server 2003.
You have to reconfig IIS 6 to handle the .RPT extension.

1.- Open IIS.
2.- Right click on "Web Sites" and choose properties (that will give you the default properties page for all the web sites).
3.- Go to the Home Directory tab, then click "Configuration".
4.- Click "Add" to add a new application extension.
5.- The executable file by default should be: C:\Program Files\Seagate Software\WCS\wcsinsapi.dll
6.- The extension is: rpt
7.- Set verbs to: Limit to: GET,HEAD,POST
8.- Click "Add" to add a new application extension.
9.- The executable file by default should be: C:\Program Files\Seagate Software\WCS\wcsinsapi.dll
10.- The extension is: cri
11.- Go to the Home Directory tab, then "Execute Permissions:"= Scripts only
12.- Open "Application Pools" Right Click on "MSSharePointAppPool"  Identity Predefined=Network Service
13.- If you check the dependencies of the Page Server service, you will see that it depends on 2 other services which are "disabled" by default on a Win2003 server. Just enable and start them and then you should be able to start the page server service
14.-Web Service Extensions: Add a new web service Extension… add… "C:\Program Files\Seagate Software\WCS\wcsinsapi.dll"… set status extension as allowed
15.- SERVER (local computer) right click "properties" "MIME types" "New…"
"Extension:" .cri
"MIME type:" application/octet-stream
"New…"
"Extension:" .rpt
"MIME type:" application/octet-stream