Yesterday I had a some scripts start failing that had been working for a couple of months without issue.
My setup is this. I have BC4 installed on Windows Server 2008 R2 Standard. I use SQL Server Agent to export web data to some text files and then call BC4 to send them up to our web servers. The SQL Server agent is logged in with and executes commands as [domain]\sqlagent. This is the only feedback I get:
The operating system command being executed is:
I've checked the following:
I've compared Process Monitor output from successes and failures and although I don't completely understand what I'm looking at I suspect it has something to do with 64 vs 32 bit. Is it a problem to be calling a 32-bit application (BC4) from a 64-bit application (Sql Server Agent)? Is there anything else I should look at? Any ideas???
My setup is this. I have BC4 installed on Windows Server 2008 R2 Standard. I use SQL Server Agent to export web data to some text files and then call BC4 to send them up to our web servers. The SQL Server agent is logged in with and executes commands as [domain]\sqlagent. This is the only feedback I get:
Message
Executed as user: [domain]\sqlagent. The step did not generate any output. Process Exit Code 1. The step failed.
Executed as user: [domain]\sqlagent. The step did not generate any output. Process Exit Code 1. The step failed.
"C:\Program Files (x86)\Beyond Compare 4\bcomp.exe" @"C:\webSiteDataExports\scripts\script.txt"
- BCProfiles.xml and BCSessions.xml have been copied in to C:\Users\sqlagent\AppData\Roaming\Scooter Software\Beyond Compare 4. I copied them after accepting the remote host's ssh key.
- The sqlagent user has all the rights it needs to read and write to the relevant folders.
- Windows Event logs... nothing gets recorded there.
- The log specified in the script. It doesn't get updated when calling the script from SQL Server. It's almost like the app is bombing before even reading the script.
- I can run the command while logged in to remote desktop on the server as [domain]\sqlagent and it works just fine.
- I've reinstalled BC4.
I've compared Process Monitor output from successes and failures and although I don't completely understand what I'm looking at I suspect it has something to do with 64 vs 32 bit. Is it a problem to be calling a 32-bit application (BC4) from a 64-bit application (Sql Server Agent)? Is there anything else I should look at? Any ideas???
Comment