Subject | RE: [ib-support] gbak: ERROR: unavailable database |
---|---|
Author | Leyne, Sean |
Post date | 2003-04-03T18:11:07Z |
Bob,
a limited "environment" so that the size of batch file and it's commands
must be limited in scope.
What I have found is that you need to create a WSF (Windows Script
File), see sample below, which runs the batch file. I then have
AT/scheduler run the WSF file, which provides a larger environment for
the batch file.
Sean
- - - - - - - -
Filename = Local_Backup.wsf
<package>
<job id="DatabaseBackup">
<script language="VBScript">
set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run( "D:\Database\Local_Backup.bat")
</script>
</job>
</package>
> >- the account that the scheduling service runs underI think you'll find that the problem is that AT/Scheduled tasks only get
> >has the proper rights in the folder with the database
> >
> >- are you using the /interactive switch of AT?
>
> It's running under the system account. This was one of my
> initial thoughts
> as well, but the same batch file was able to create a backup
> to a single file in the same folder.
>
> Interactive is false. No change from before.
a limited "environment" so that the size of batch file and it's commands
must be limited in scope.
What I have found is that you need to create a WSF (Windows Script
File), see sample below, which runs the batch file. I then have
AT/scheduler run the WSF file, which provides a larger environment for
the batch file.
Sean
- - - - - - - -
Filename = Local_Backup.wsf
<package>
<job id="DatabaseBackup">
<script language="VBScript">
set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run( "D:\Database\Local_Backup.bat")
</script>
</job>
</package>