Changed behavior with Shell-commands in NAV 5.0???

sander7

Hi guys,

I have had a NAS run a BAT-file, that fetches some files through ftp.
It have run for some time on a 4.0 SP3, without any problems.

Last week we did a technical upgrade to NAV 5.0, and ever since the NAS hasn't been able to run the BAT-file.
It keeps getting the security-warning.

I use the WSHShell.RUN command.
I have put the command itself into a text-var.
And remember it ran flawless in 4.0 SP3...

What has changed, and how can I work around it

Update:
#-o
Apparently I was mistaking about the security-warning...
I have now changed my functionality, so that it uses a Job Queue, and from the log, I see that the actual error is "An exeption was raised in method Run........."

I tried to run the report (the one that do the WSHShell-call) from within an ordinary NAV-client. The report runs perfectly, and my files are fetched as it should.
I then tried to run the NAS in a command-prompt, to see if I could catch some more info. Again the report runs perfectly.
So it is only if the NAS run as a service, that the error comes.
(I have the service use my domain-account, to exclude any differences in user-rights)

Any ideas?

kriki

Have you tried the NAS using the domain-admin account?

sander7

Hi Alain,

No I haven't tried that.
But we also had it run with my domain-account for a while in 4.0, and didn't have any problems.
If the IT-dep. will allow it, I'll try having the domain-admin run the service.

I'll get back with an update.

sander7

:roll: :oops:
The bat file was moved to a network-drive together with the upgrade.