Execute a DTEXEC batch file (.bat) in an AUTOMIC windows job

[Anon Anon]

 

Hello,

 

 

I am trying to execute a DTEXEC batch file (.bat) in an AUTOMIC windows job, but the job seems to be looking on the AUTOMIC server not the target server for the executable.    The job fails every time saying it can’t find DTEXEC.  We moved a copy of DTEXEC to the AUTOMIC server, and the job stopped failing, but of course nothing happened because SQL server is not running on that box.

 

 

 

Here are the contents of my batch file:

 

echo Loading BPC Data

 

dtexec /f "E:\PC_MS\Data\Webfolders\Madeira\Landing\DataManager\PackageFiles\CustomFiles\Load_BPC_Data_All.dtsx"

 

echo %errorlevel%

 

pause

 

exit /b %errorlevel%

Any help would be very much appreciated.

Rich Wittich

Lumber Liquidtaors

 

[Anon Anon]

I think you should look into the /Ser[ver] parameter of dtexec. By default a dtsx runs at localhost but you can override it with this parameter (seelink)

The dtexec.exe should be available at the server where the Windows Agent running the job is installed. From your description I think that is the AUTOMIC server you are talking about.

Good luck! 

[BryanCain601034]

I work with Rich - let me see if I can clarify a little.

We have Automic/UC4 connected to a Windows server, call it WINSERVA.  We are trying to execute a batch script that lives on WINSERVA.  Said batch script references c:\...\dtexec .  The script continually errors saying it can't find dtexec.   

The only thing we found that stopped this error was copying dtexec off of WINSERVA and onto the Automic/UC4 application server.  But of course, since SQL Server doesn't live on that box, the executable didn't actually do anything.

For some reason it appears that the automation engine is trying to run the .bat file locally rather than on the target server.

I've attached screenshots of the windows tab and the process tab.  I think we must be doing something wrong in one of them.

Thanks in advance - we are pretty new at this.

[Legacy User]

Bryan, The dtexec should be on a Host Windows server as you described. Fully qualify your dir path and enclose in Quotes.Pass your parms after. Example: "c:\Program Files (x86)\Microsoft SQL Server\100\DTS\Binn\DTExec.exe" /file "\\DBsqlserv\ssis$\example\sub\dir\example.dtsx" /De it2lock

[Anon Anon]

Hello Bryan,

As Jesse states; dtexec is a program that can be run on any Windows server and configured to connect to any remote dtsx file or database server. If you try to start the executable (with a batch file or direct) with a Windows agent, the Dtexec.exe must be available at the server the agent is installed on.

So if you want to run a dtsx package from that server, you should install the SQL server client tools (or maybe just copying the executable as you did).

Regards,
Jeroen 

[BryanCain601034]

So, figured out what the problem is - yet another example of us being new at this.  It seems that most agents can be installed on the central Automic host - I didn't know that, I thought they were all installed on the target host.

Our netops team didn't know what windows hosts must be installed on the target.  Once we realized what was going on and installed the agent locally on the target the job worked perfectly.

Thanks for all the replies.

[Anon Anon]

Thanks to all for the suggestions!