Actually if someone who has worked with SSIS could give me a heads up on the file connection manager issue, that would be great.

The file connection manager is not reading...

I am actually trying this in SSIS simultaneously, but I am having several problems with it:

The ssis file is not reading the number of columns correctly, it is dropping some...

Good!  Thanks for the input

KR

Ok, did the change on startup accounts, that did not help.  I do see a certificate under computer account/personal.

From what I have observed so far, with the fact that this...

I will try that and let you know

Thanks

KR

Domain User - This has now happend to three of our test installations - one install and two upgrades.  None of them created the crypto folder for the startup account...

There is not crypto folder for the sql startup account - In fact it is not in any other folder except in the user who installed the sql server?

Thanks

KR

Yes,  I do find both of those errors in the error logs -

except the error number is 1.

Fallback certificate initialization failed with error code: 4

Warning: encryption is not available,...

Yes, that worked!

Thanks much

KR

Yes, that worked,  Thanks so much

KR

Hi,

It was not a rights issue after all -  the master database somehow did not get upgraded to sql 2005 version like it should have(I am still trying to find...

No, that was not it,  I found the problem -  our password had some special characters that did not work well in command prompt.  Once I removed those( &, +)...

Yes, it does seem that way by looking at the error - only the account is in the local admin group for the box and in the system administrator fixed role on...

I did run the upgrade advisor, there were no warnings that needed taken care of before the upgrade.  There were warnings about some stored procedures that had syntax that would...

The upgrade advisor did show any problems with the upgrade other than some ols syntax issues in the stored procedures to correct after the upgrade. 

I was on service pack 4