Thread: pgAdmin Job fires wrong .bat file

I just created a job with pgAdmin.  One of the steps is to kick of a .bat file at C:\PostgreSQL\PG_backups.bat.  I
couldn'tfigure out why this wasn't being triggered so I turned the logging to debug on my pgAgent Service.  Instead of
lookingfor my .bat file at C:\PostgreSQL\PG_backups.bat it looks for it at
"C:\DOCUME~1\ADMINI~1.UC\LOCALS~1\Temp\pgaCB.tmp\1_1.bat".Anyone have any clue why it would be looking in a temp
directory? 

On Fri, Dec 11, 2009 at 9:51 PM, Jason Sanford <jasonsanford@gmail.com> wrote:
> I just created a job with pgAdmin.  One of the steps is to kick of a .bat
> file at C:\PostgreSQL\PG_backups.bat.  I couldn't figure out why this wasn't
> being triggered so I turned the logging to debug on my pgAgent Service.
> Instead of looking for my .bat file at C:\PostgreSQL\PG_backups.bat it looks
> for it at "C:\DOCUME~1\ADMINI~1.UC\LOCALS~1\Temp\pgaCB.tmp\1_1.bat". Anyone
> have any clue why it would be looking in a temp directory?

The command that you tell it to run gets written to a temp file which
is then executed. So if the job step contains:

@echo off
C:\PostgreSQL\PG_backups.bat

Then that is written to the temp file and executed.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com