Re: Error on 64 bit systems...

Here's one more experiment that should give us a bit more insight into what's happening. Try logging on to the 64-bit system and running the script from that system against itself and against other servers.

At this point, we're not seeing any errors that would indicate breakage in WMI or an odd configuration, so the problem is apparently rather well-hidden. Running the code on the 64-bit server will fill in the picture.

+ If it fails to run, there's a clear local problem of some kind with WMI configuration or permissions.
+ If it runs ok locally but doesn't run against the remote systems, there's a symmetric problem - likely something with the credentials being used.
+ If it runs ok locally and against remote servers, we know that the problem apparently only shows up calling from your 32-bit server to the 64-bit server. We also know of one workaround, albeit a weird one - run from the 64-bit system.

"thestriver" <bijusinbox@xxxxxxxxx> wrote in message news:44750ccb-8800-4cdb-b79f-4891fe26117f@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 7, 3:27 pm, "Alex K. Angelopoulos" <aka(at)mvps.org> wrote:
I'm not having any trouble with this against Vista x64, which suggests the
problem is not64-bitness but security settings for the specific system in
question. I suggest checking the following:

+ try to ping the machine in question (as well as any other64-bitservers
you have, as a comparison). If it drops ping requests, the firewall is
probably configured very tightly. If it lets them through, the problem is
more specific to WMI, and may even be an issue with a corrupt WMI
repository.

+ Confirm whether the system is just an average server, or has a special
configuration that may be causing security problems. Those would include a
distinct domain role (being a member server only, for example, or not a
domain member) or a special version such as SBS - unlikely given what you've
said, but still possible.

+ Check the event logs on the system in question. I recall some of the
2006-2007 era patches causing possible problems with DCOM that could
interfere with WMI. You'd be looking specifically for the following issues:
blanket errors with the DCOM subsystem, WMI, or the Windows Firewall; and
repeated remote authentication failures.

+ One other thing: is the account you are using to connect to the remote
system in question one with local as well as domain administration
privileges on the system in question?

"thestriver" <bijusin...@xxxxxxxxx> wrote in message

news:c2a93d36-af1f-48f2-a22f-6901420b8856@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



> Hello,

> I'm trying the following script on 32bitremote servers and it is
> working great. However, as soon as I use this same script to run on64
>bitsystems, it gives me the errors mentioned after the script below:

> 'OnErrorResume Next
> Const HKEY_LOCAL_MACHINE = &H80000002
> strServer = InputBox("Enter Server Name here: ")
> strServer = Trim(strServer)
> If IsEmpty(strServer) Then
> WScript.Echo "You have to enter a valid Server Name...ending Script"
> ElseIf Len(strServer) = 0 Then
> WScript.Echo "You have to enter a valid Server Name...ending Script"
> Else
> Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" &
> strServer & "\root\default:StdRegProv")
> strKeyPath = "SYSTEM\CurrentControlSet\Control\Session Manager
> \Environment"
> strValueName = "PROCESSOR_ARCHITECTURE"
> oReg.GetStringValue HKEY_LOCAL_MACHINE, strKeyPath, strValueName,
> strValue
> If strValue = "x86" Then
> WScript.Echo "32bitOS"
> Else
> WScript.Echo "64bitOS"
> End If
> End If

>Error:
> C:\BT\Scripts\2003SP2Auto\32or64.vbs(19, 1) Microsoft VBScript runtime
>error: Th
> e remote server machine does not exist or is unavailable: 'GetObject'

> Note: I'm trying to run the above script from a 2003 SP2 32-bitserver
> and entering a remote64-bitserver name at the prompt.

> Please help !- Hide quoted text -

- Show quoted text -

I can ping them and others just as well as pining any 32 on the same
domain.
Is a member app server with similar fqdn as 32 bits. Nothing
extraordinary about its their builds.
No authentication errors in eventvwr and can't stop dcom as other apps
on it require it.
I use an admin account to try out the scripts and it has has local
admin rights as well.
Thanks for your effrots...

.

Relevant Pages

  • RE: Does WMI have to be installed on Remote Computer?
    ... IMHO this looks like a well constructed and very vell commented script. ... WMI comes as standard on w2k w2k3 and xp, ... does WMI need to be installed on the remote computer in order for a ... ''' First try to ping the server. ...
    (microsoft.public.scripting.vbscript)
  • Re: Remote office logon script - Long Delay
    ... Windows IP Configuration ... If I point the User's profile to a script that doesn't contain the ... I do not have WINS configured for the remote site, ... This remote server was built using connect computer script, ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote office logon script - Long Delay
    ... Windows IP Configuration ... If I point the User's profile to a script that doesn't contain the ... I do not have WINS configured for the remote site, ... This remote server was built using connect computer script, ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote office logon script - Long Delay
    ... Windows IP Configuration ... If I point the User's profile to a script that doesn't contain the ... I do not have WINS configured for the remote site, ... is a GC/AD server with DNS and DHCP for it's area. ...
    (microsoft.public.windows.server.sbs)
  • Does WMI have to be installed on Remote Computer?
    ... I'm new to WMI, learning as I go. ... does WMI need to be installed on the remote computer in order for a ... script which uses WMI to work? ... ''' First try to ping the server. ...
    (microsoft.public.scripting.vbscript)