I have a requirement in my SSIS packages to read and write files on network file servers. In development, I was able to get this working cleanly by using my AD account as the SQL Agent service account. My userid is in the server sysadmin role and have
read/write access to the file server.
But for production use, my organization doesn't allow the creation of Active Directory service accounts and I obviously cannot use an individual account, so that is not an option for my SQL Server & SQL Agent service accounts.
I decided to test out using a virtual service account on my dev server. I gave the machine account (virtual account) read/write access to the required network directories.
I changed SQL Agent to use NT SERVICE\SQLSERVERAGENT and restarted the service. But when I run the job that calls the SSIS package, now I get this error in Job History:
Error: 2012-12-12 12:47:54.44 Code: 0xC001401E Source: LSS Master Package Connection manager "SQL Report Tables.dtsx" Description: The file name "\\LSSFLSVR\Data\2011_DEV\BIDS\LSS Current\LSS Current\SQL Report Tables.dtsx" specified in the connection was not valid. End Error
That UNC connection is what I use when debugging in BIDS. But prior to building a deployment manifest I change the master package to read its child packages from SQL Server storage.
This works as expected with the SQL Agent service account set to my Windows login. I don't understand why changing the service account to a virtual account would change the connection managers of the child packages.
I would really appreciate any guidance as to what other settings might need to be changed....documentation on virtual service accounts for SQL Server services is thin as far as I can tell.
But for production use, my organization doesn't allow the creation of Active Directory service accounts and I obviously cannot use an individual account, so that is not an option for my SQL Server & SQL Agent service accounts.
I decided to test out using a virtual service account on my dev server. I gave the machine account (virtual account) read/write access to the required network directories.
I changed SQL Agent to use NT SERVICE\SQLSERVERAGENT and restarted the service. But when I run the job that calls the SSIS package, now I get this error in Job History:
Error: 2012-12-12 12:47:54.44 Code: 0xC001401E Source: LSS Master Package Connection manager "SQL Report Tables.dtsx" Description: The file name "\\LSSFLSVR\Data\2011_DEV\BIDS\LSS Current\LSS Current\SQL Report Tables.dtsx" specified in the connection was not valid. End Error
That UNC connection is what I use when debugging in BIDS. But prior to building a deployment manifest I change the master package to read its child packages from SQL Server storage.
This works as expected with the SQL Agent service account set to my Windows login. I don't understand why changing the service account to a virtual account would change the connection managers of the child packages.
I would really appreciate any guidance as to what other settings might need to be changed....documentation on virtual service accounts for SQL Server services is thin as far as I can tell.