Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
bensalem Absent Member.
Absent Member.
290 views

Scripting driver fail to run a vbs script


Hi,

I'm trying to run a vbs script using the scripting driver. The
following error appears when the driver tries to create a temporary
file:

Message = Error creating temporary file for object
\IDV\Company\Persons\Test123 (code 183). Event discarded.

Later in logs I can see this trace:

2011-12-28 16:08:36 [1120@3592] (trace): WindowsScript query handler
creating input document
2011-12-28 16:08:36 [1120@3592] (trace): D:\Temp\WSDDF4.tmp
2011-12-28 16:08:36 [1120@3592] (trace): Couldn't create event file
D:\Temp\WSDDF4.tmp: error code 5
2011-12-28 16:08:36 [1120@3592] (trace): WindowsScript query handler:
complete

The account running the service has an admin rights.

Do you have an idea, how to solve this issue?

Thanks in advance.


--
bensalem
------------------------------------------------------------------------
bensalem's Profile: http://forums.novell.com/member.php?userid=77835
View this thread: http://forums.novell.com/showthread.php?t=450064

Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Scripting driver fail to run a vbs script

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Google says that error 5 is access denied. How did you make this
account an admin? Is it an "admin" type of thing that has filesystem
rights as you would expect? Has this worked in the past? Does it work
on other (test, qa, prod) systems?

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJO+07IAAoJEF+XTK08PnB5DOkQAKSTNVpaz2zkqmCz8t3NDSwg
1gcxtoJ5u5vNNeoYImGl21wnC50YnaAGgVB+1n1WELcbuYZMCF4iofs8+HeZhlc0
0JMpO8E87ak27u1L+Ev/o52CZTlXhirc0bSlzl3m23FC9azBbEuygLuyDnYEf8M3
CPOXOhZEzR6l74FpLpZWvvMqVbTQUmAQsG37xc2qFQIiMDNaJXiAXL4NsPdlGQng
VM25TbnFxtepDstHXp5VFGjy6fOE1DDsXzF54cBEwK5EHjaPgnL2iGf/WlFA5w7l
kgABcAvekOlwCbuGp9WcIRgq+3Y7f8MOawWm1Nc56LbzTAJetsDplG9iF/pF4yBn
L+Od5PpOO4JBHJ4TynwR10ZBG32hVYYEKVvPhRF+PXLpRnp3W9tVe+RSDWCtkK0M
FJLfsR6Yxvp5a9nAMsW2d/Ep4EhqvuWb2fWG1nq/UGSC0lkArjwGRzh7Q+GtgKd1
T1eeJfUsAK94OF+/qoign/Eyl0/+sCmrR1y4WbwwjeVymn90oZlEnBG3KwQ8LzxT
OXl2oYJ/M/XE7yCKp1AEQggqOlDcukgFMTCdQoewqbZAhprb9EsnDgcQvITrLsSQ
RvepkZWUdeavCDLnNLhUFK8ClJgIec8t7b4U4gTKGICE9nii4KzfiOiteEIe6Xvi
elMlHFsXunpWXLH4fZ+y
=2yeH
-----END PGP SIGNATURE-----
0 Likes
Knowledge Partner
Knowledge Partner

Re: Scripting driver fail to run a vbs script

I think the script driver uses EFS to encrypt the temporary files it
creates. Make sure that the EFS certificate is valid.

On 28/12/2011 16:36, bensalem wrote:
>
> Hi,
>
> I'm trying to run a vbs script using the scripting driver. The
> following error appears when the driver tries to create a temporary
> file:
>
> Message = Error creating temporary file for object
> \IDV\Company\Persons\Test123 (code 183). Event discarded.
>
> Later in logs I can see this trace:
>
> 2011-12-28 16:08:36 [1120@3592] (trace): WindowsScript query handler
> creating input document
> 2011-12-28 16:08:36 [1120@3592] (trace): D:\Temp\WSDDF4.tmp
> 2011-12-28 16:08:36 [1120@3592] (trace): Couldn't create event file
> D:\Temp\WSDDF4.tmp: error code 5
> 2011-12-28 16:08:36 [1120@3592] (trace): WindowsScript query handler:
> complete
>
> The account running the service has an admin rights.
>
> Do you have an idea, how to solve this issue?
>
> Thanks in advance.
>
>

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.