Re: Win32::NetAdmin

Try inserting a delay (sleep) just before the failing call. Start with something like 10 or 15 seconds and if that fixes the problem, slowly reduce the delay until problem comes back.

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller
If I understand your problem, I can solve it! Of course, the same can be said for you.

Comment on Re: Win32::NetAdmin

Replies are listed 'Best First'.
Re: Re: Win32::NetAdmin by devslashneil (Friar) on Aug 12, 2003 at 00:13 UTC
Yeah sorry i could have mentioned that, i even tried a sleep for 10 minutes but it didn't fix it :\ Neil Archibald - /dev/IT -	[reply]
Re: Re: Re: Win32::NetAdmin by BrowserUk (Patriarch) on Aug 12, 2003 at 08:25 UTC
I can't reproduce this with AS 5.6 (633) / 5.8 (802) and Win32::NetAdmin v0.08. One thing I just noticed is that you are printing $^E (which looked fine to me first time around), but then I noticed that the pod for NetAdmin says When a function fails call Win32::NetAdmin::GetError() rather than GetLastError() or $^E to retrieve the error code. It's just possible that you are looking at the wrong error message? Have you tried this from another machine? Under a different account? On the domain server? Which versions of OS, perl, the module etc. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "When I'm working on a problem, I never think about beauty. I think only how to solve the problem. But when I have finished, if the solution is not beautiful, I know it is wrong." -Richard Buckminster Fuller If I understand your problem, I can solve it! Of course, the same can be said for you.	[reply]