Re^3: Win32::TieRegistry: Remote connect problems

Check the event log of the receiving machine.

If you see "Event 36; ...the configured identity is incorrect...", you may have a conflict in the passwords which are supposed to be shared by IIS, DCOM and MTS, but got out of sync.

More info on this in MS KB article 297989.

"As you get older three things happen. The first is your memory goes, and I can't remember the other two... " - Sir Norman Wisdom

Comment on Re^3: Win32::TieRegistry: Remote connect problems

Replies are listed 'Best First'.
Re^4: Win32::TieRegistry: Remote connect problems by mrlifeguard (Initiate) on Mar 13, 2008 at 17:57 UTC
is there any other way to connect to a remote registry?	[reply]
Re^5: Win32::TieRegistry: Remote connect problems by NetWallah (Canon) on Mar 13, 2008 at 18:55 UTC
Yes - according to the docs, you could prepend your key with "//$machine/", and do a regular registry open (instead of connect). I also strongly recommend following Browseruk's suggestion, and displaying $^E when you call "die". "As you get older three things happen. The first is your memory goes, and I can't remember the other two... " - Sir Norman Wisdom	[reply]