question

Noonies avatar image
Noonies asked

SQL Job stating that a connection was not valid on an XSL file

I'm receiving an error on a package I created which uses XSL file. I noticed I receive the following error: 

Description: The file name "C:\Users\\Documents\Visual Studio 2008\Projects\Packages\Product Transfers Daily\Product Transfers Daily\ProductTransfers-Whses.XSL" 
specified in the connection was not valid.
I can run the package fine in BIDS without any issue which leads me to a permissions issue but permissions have not changed and all other packages are working fine. Is there something I am overlooking? This job worked fine for the last year or more. If I have not given enough information please let me know and I will provide.
ssisbids
6 comments
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Shawn_Melton avatar image Shawn_Melton commented ·
I would suggest moving the file out of the profile (Users) directory. I would place it on a central folder on the server, then ensure the account has specific rights to the folder/directory.
1 Like 1 ·
Shawn_Melton avatar image Shawn_Melton commented ·
So the file and path is local on the SQL server the package is running from?
0 Likes 0 ·
Noonies avatar image Noonies commented ·
Yes it is local on the SQL Server. I have deployed the package to SQL Server so it shows in MSDB and fails when running in there. The job Step properties looks at the SQL Server for the Package Source, the server name is entered, and the package: is set to the Package Name. Hope this answeres your question.
0 Likes 0 ·
Shawn_Melton avatar image Shawn_Melton commented ·
Have you verified that the service account SQL Server Agent is configured to has rights to the location of that file?
0 Likes 0 ·
Noonies avatar image Noonies commented ·
Yes! I have the account in the server administrators group. Should I try to add it separately for permissions?
0 Likes 0 ·
Noonies avatar image Noonies commented ·
Hi Shawn! Thanks again for all your help! I noticed that this did tie to permissions. I had a broken SID due to an account being migrated to a new domain. Though the account was part of the Administrators group, this was not allowing appropriate permissions for whatever reason. I have readded the account to have access to the files. I will take your suggestion when I move the SQL server from physical to VM this weekend. Thank you again - your time is greatly appreciated!
0 Likes 0 ·

2 Answers

·
Noonies avatar image
Noonies answered
Hi Shawn! Thanks again for all your help! I noticed that this did tie to permissions. I had a broken SID due to an account being migrated to a new domain. Though the account was part of the Administrators group, this was not allowing appropriate permissions for whatever reason. I have readded the account to have access to the files. I will take your suggestion when I move the SQL server from physical to VM this weekend. Thank you again - your time is greatly appreciated!
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

DharmanDave avatar image
DharmanDave answered
Hi... Try running it by selecting '32-bit Runtime' in the job step.
1 comment
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Noonies avatar image Noonies commented ·
I had tried that. I need to mark my last comment to Shawn as the issue and post as an answer. Thank you for taking a look at this DharmanDave.
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.