principal to proxy problem

I can successfully execute my package via Business Studio but when I schedule it in SQL Agent I get the error message, 'could not get proxy data for proxy id = 2.' I am trying to execute the scheduled job with that proxy (call it abcd_proxy) because I have a logon id (call it abcd) with access to a specific network drive folder, which holds a required source flat file. The abcd logon is defined as a sysadmin account. I am unable to see that the abcd logon id is an added principal within the abcd_proxy, which I think is because the abcd logon principal has a sysadmin role. My proxy id = 2 definition looks to be defined the same way that my first proxy id was.

Does anyone have an idea about what the message means and how I can fix it?

I had to create a proxy recently to have an SSIS package write a file to a network folder. I am by no means an expert on the subject, but here is what I had to do.

I had to first create a windows account with the right credentials. I then created a credential, a proxy for the credential, and of course set the "Run As" parameter for the step to the proxy. I made sure that the new account was added as a sysadmin in SQL Server, added the account to the "Users" group on the server, as well as to the Logon as batch security policy. When I still had problems with the package being able to read a file it was related to the credentials of the account, which I had the network admin fix. Everything now runs fine.

I apologize if I have stated the obvious to you, but just wanted to share with you all the steps I had to take to perform a task very similar to what you are trying to do. Of course, I had to also use an "absolute" network path and not a mapped drive letter.

Hope this helps.

principal db in "principal, synchronizing" state, the mirror in "restoring"

We have mirroring setup for 5 dbs, 4 of which are synchronized and 1 which is in "synchronizing" state on the principal and "restoring" state on the mirror. Mirroring for all dbs has been working fine for the past several months and we have a witness that has allowed automatic failover in the past without problems.

This database has several bulk inserts performed throughout the day and am sure there is some latency due to the size of these transactions.

Not sure as to why this is happening all of a sudden, but the db in question has been in this state for the past 12 hrs. I checked the mirroring status on the principal and it states that it is "synchronizing: data is being transferred from principal to mirror", but the mirror server states that db is in "restoring" state. Can anyone suggest as to how I can get the database on the mirroring server to get back to "mirror, synchronizing/restoring..." state? Or suggest on how I can troubleshoot this?

Thanks in advance.

Have you tried pulling up the Database Mirroring Monitor, to see what it shows? Do you have Unsent Log or Unrestored Log? Does the I/O subsystem on the mirror have comparable I/O capacity to the Principal?

Principal 64Bit- Member on 32Bit

Hi all,
I've got two VLDBs on 64bit hardware platform + 64Bit-W2003K Std R2 + 64Bit SQL2005 Std Edition.
If I set this guy up as the Principal, can I have the standby/member on 32Bit HW + 32Bit W2003 Std + 32Bit SQL2005?

Will this actually work?

Regards,
Uday ShivamurthyCome on guys, I've had 55 views and not a single reply. Someone offer views please.Regards,Uday Shivamurthy|||Theoritically I don't see any difference or issue in setting up this way, http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1015569&SiteID=1 fyi.|||Database Mirroring between 64 bit principal and 32 bit mirror is supported. However, please understand the ramifications when you failover. After you failover, the 32 bit machine now becomes the principal and it may not perform the same way as the 64 bit principal was performing.

Principal 64Bit- Member on 32Bit

Hi all,
I've got two VLDBs on 64bit hardware platform + 64Bit-W2003K Std R2 + 64Bit SQL2005 Std Edition.
If I set this guy up as the Principal, can I have the standby/member on 32Bit HW + 32Bit W2003 Std + 32Bit SQL2005?

Will this actually work?

Regards,
Uday ShivamurthyCome on guys, I've had 55 views and not a single reply. Someone offer views please.Regards,Uday Shivamurthy|||Theoritically I don't see any difference or issue in setting up this way, http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1015569&SiteID=1 fyi.|||Database Mirroring between 64 bit principal and 32 bit mirror is supported. However, please understand the ramifications when you failover. After you failover, the 32 bit machine now becomes the principal and it may not perform the same way as the 64 bit principal was performing.