STEXPORT.EXE Windows 2003 Task Scheduler

[Guest]

I can't get a scheduled job to run using Server 2K3 Task Scheduler. The stexport.exe process just hangs no cpu use.

The job runs manually, and from the batch file (Below) if executed interactively.

I have a scheduled job as follows c:\batch\ExporterPro\export.bat
Doesn’t work if I just schedule as follows: c:\batch\ExporterPro\stexport.exe /CONFIG="C:\Batch\ExporterPro\Configs\Systems Export - Config.INI"

Works fine as long as the "logged on User" is the credentials you use for the task.

It should work with no one logged on, shouldn’t it?
I know the account I'm using has sufficient access to the servers and domain. You can logon to that account interactively and it works fine locally.

(export.bat)
@ECHO OFF
REM Kill any Exporter Pro Process(s)
C:\BATCH\PROCESS.EXE -K stexport.exe

TITLE Exporter Pro - Systems Export - Exporting...
ECHO Exporter Pro - Systems Export - Exporting...
c:\batch\ExporterPro\stexport.exe /CONFIG="C:\Batch\ExporterPro\Configs\Systems Export - Config.INI"
ECHO.

TITLE Exporter Pro - AD Export - Exporting...
ECHO Exporter Pro - AD Export - Exporting...
c:\batch\ExporterPro\stexport.exe /CONFIG="C:\Batch\ExporterPro\Configs\AD Export - Config.INI"
ECHO.

TITLE Exporter Pro - NT4 Domains - Exporting...
ECHO Exporter Pro - NT4 Domains - Exporting...
c:\batch\ExporterPro\stexport.exe /CONFIG="C:\Batch\ExporterPro\Configs\Configs\NT4 Domains - Config.INI"
exit

[Guest]

Re: STEXPORT.EXE Windows 2003 Task Scheduler

I figured it out...
Hyena License Key dialog box causing the hang up.

Licensing Info For Hyena is stored in HKCU Hive of the Registry thus user specific.
Had to enter license info and default "ConfigurationFileDirectory" for the account that runs the scheduled job.

Works as expected now.

Did you do this for terminal services users to better enable license compliance?


[This message has been edited by L (edited 05-02-2008).]

[kstanush]

Re: STEXPORT.EXE Windows 2003 Task Scheduler

Glad you got it figured out before we had a chance to tell you this is what the problem is. We see it a lot. Mostly, it happens when someone follows Microsoft's advise and runs Hyena or any utility under a different set of credentials, which creates the same problem. Forever, Microsoft's advice was to place all application settings under HKCU, but looking back this has caused a lot of problems like this.

I'll need to revisit why our mechanism to place the license key information into a file is not working.

The problem, again by Microsoft's creation, is that applications are not supposed to place any data into the installation directory. This was one of the many reasons that we don't try to get our applications 'certified' because doing so requires you to do things Microsoft's way vs. the best way given the situation. Applications were supposed to put all data or configuration information into the profile directory, but this is no better than the HKCU registry as its user-specific. Worse, Vista now prevents applications from writing into the installation directory. All this means is that is very difficult to have a 'common' area for anyone running the application for things as simple as the license key.