February 6, 2012 at 4:57 am
We've managed to fix the problem.
The registry key pointing to the msdtssrvr.ini.xml file was pointing to D:\Program Files\Microsoft SQL Server\100\Binn
it should have been D:\Program Files(x86)\Microsoft SQL Server\100\Binn
🙂
February 6, 2012 at 5:00 am
It sounds as if the file was in the wrong place and the registry entry was correct, since you said that everything was 64-bit.
John
February 6, 2012 at 5:03 am
interesting - as far as i'm aware the files haven't been moved....
i'll have to do some more digging then
February 6, 2012 at 5:13 am
Possible explanation
Quote:
By default, a 64-bit computer that has both the 64-bit and 32-bit versions of an Integration Services command prompt utility installed will run the 32-bit version at the command prompt. The 32-bit version runs because the directory path for the 32-bit version appears in the PATH environment variable before the directory path for the 64-bit version. (Typically, the 32-bit directory path is <drive>:\Program Files(x86)\Microsoft SQL Server\100\DTS\Binn, while the 64-bit directory path is <drive>:\Program Files\Microsoft SQL Server\100\DTS\Binn.)
http://msdn.microsoft.com/en-us/library/ms141766.aspx
May 22, 2012 at 5:59 am
Had this same issue again but this time it was because the instance name was NOT specified in the config file when it should have been.
Thought it would be useful to post up the fix here 🙂
http://msdn.microsoft.com/en-us/library/ms137789.aspx
Viewing 5 posts - 16 through 19 (of 19 total)
You must be logged in to reply to this topic. Login to reply