910207 - 3 problems

Re: 910207 - 3 problems

Postby hamidi » 15.05.2012, 06:02

ok, i did. all three scripts/batch files ran successfully, and after running them i executed 'set' to see whether OS_NAME is set and saw that it has been set to wxp. then i looked into SetSystemEnvVars.cmd and found that no entry for OS_NAME is there in the file. then found that it has been set in SetTargetEnvVars.cmd.
now what can i do?
thx
hamidi
 

Re: 910207 - 3 problems

Postby rinkol » 16.08.2012, 19:51

I've run into a situation where, on one particular computer, the installation of updates would terminate prematurely with a statement "Nothing to do!. I'm not sure if it applies here, but I found that the WSH timeout had been set to one (1) second in the registry. By setting it to "0", the value for no limit, the problem was fixed. I have no idea of how it got changed in the first place.
rinkol
 

Re: 910207 - 3 problems

Postby harry » 16.08.2012, 21:03

@rinkol
For clarification I have the question: Do you mean the following key?
Code: Select all
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Script Host\Settings]
"SilentTerminate"="0"

harry
 
Posts: 737
Joined: 29.10.2009, 17:02

Re: 910207 - 3 problems

Postby rinkol » 16.08.2012, 23:41

No. the WHS timeout key is located under HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings.

It should appear as

Timeout REG_DWORD 0x00000000 (0)
rinkol
 

Re: 910207 - 3 problems

Postby harry » 17.08.2012, 00:52

Thanks for information!

By default the key HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings is empty.
harry
 
Posts: 737
Joined: 29.10.2009, 17:02

Re: 910207 - 3 problems

Postby WSUSUpdateAdmin » 17.08.2012, 10:50

Hi!

rinkol wrote:[...], but I found that the WSH timeout had been set to one (1) second in the registry. By setting it to "0", the value for no limit, the problem was fixed.[...]

Which key do you talk about? I can't find a "WSH timeout".

harry wrote:By default the key HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings is empty.

Correct, harry, but by default the key [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows Script Host\Settings] contains:
Code: Select all
"DisplayLogo"="1"
"ActiveDebugging"="1"
"SilentTerminate"="0"
"UseWINSAFER"="1"

, where both "UseWINSAFER" and "SilentTerminate" seem to deal with signed/trusted scripts (and not timeouts).
By "quick search", I only found http://books.google.de/books?id=_OmVAgsGkBYC&pg=PA178&lpg=PA178&dq=SilentTerminate+windows+script+host&source=bl&ots=ZJ7ozqwzyr&sig=uwH6IfBnbiJzkQUg7gbwKu-LAgc&sa=X&ei=6w8uUMOjPIjzsgbqhIHADQ&ved=0CCkQ6AEwCA#v=onepage&q=SilentTerminate%20windows%20script%20host&f=false to prove that, but only http://technet.microsoft.com/en-us/library/ee198684 and http://technet.microsoft.com/en-us/library/ee156597 at Microsoft's site.

RTW
WSUSUpdateAdmin
Administrator
 
Posts: 2245
Joined: 07.07.2009, 14:38

Re: 910207 - 3 problems

Postby harry » 17.08.2012, 11:27

I think, rinkol means:
[HKEY_CURRENT_USER\Software\Microsoft\Windows Script Host\Settings]
Code: Select all
"Timeout"=dword:00000001

source: http://www.visualbasicscript.com/WIERD-PROBLEM-Can39t-set-timeout-for-vbscript-m63268.aspx
harry
 
Posts: 737
Joined: 29.10.2009, 17:02

Re: 910207 - 3 problems

Postby WSUSUpdateAdmin » 17.08.2012, 11:48

Oh ja, danke, das wusste ich nicht!
Na dann: Raus damit! :)
GT
WSUSUpdateAdmin
Administrator
 
Posts: 2245
Joined: 07.07.2009, 14:38

Previous

Return to Installation / Updating

Who is online

Users browsing this forum: Google [Bot] and 65 guests