WinBatch Tech Support Home

Database Search

If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.

TechHome

winbatch
networks - servers
Microsoft Client
Errors

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Wil Extender Error 601 and 531 

Keywords: 	   Wil Extender Error 601 and 531 Invalid Parameter

Question:

I upgraded to the latest compiler and Dll's and I am still getting the Wil Extender Error 601 error, which seems like it has something to do with the logon accounts/servers/domains..

So I have tried some other commands. 

	Groups = w9xMemberGrps("\\server",UserName,@GlobalGroup,0)
returns 
	Error 531:Invalid parameter
Also I get the same error on w9xMemberGet.

Any ideas what these calls rely on? the RAdmin and RLocal Dll files are in the same directory. and it happily complains about them if they are not there.

Everything else on the PC seems to work fine. No errors when logging in. The computer has access to everything in the Domain that they should.

Answer:

Sounds a bit like the Office uninstall bug that trashes parts of windows. (see a little further down in this article.)

The trick is to determine which parameter it's complaining about, by using other functions. First try w9xListGroups to make sure the server name is okay. Then w9xMemberList will tell you if the group name is okay, and w9xMemberGrps will tell you if the user name is okay.

  1. I would closely check server and usernames. The error means invalid parameter. Check the server and username parameters your passing to make sure they are in the correct format, with hard-coded values.

  2. Look in your Windows directory for a file called WWWBATCH.INI Sometimes additional error information may be found in there. Make the error occur then look into the WWWBATCH.INI file and see if anything in there looks interesting. If there is something, we can look up the extended error codes. If the number is 87, 87 = invalid parameter (see above).

    Use the latest version of the extender to do it. Use a fully qualified path in the AddExtender line to make sure you are getting the extender you think you are.

  3. Really closely compare all settings in the Control Panel network applet to look for incorrect configuration.

  4. Make sure it's really a vanilla NT server. Does it have something like Citrix or some other non-vanilla setup on it? Try different server and/or user names, if possible, or from a different machine.

  5. Check type of logon. Domain logon? Local Machine logon? What logon options are used. See Control panel Password applet.

  6. Check user account on domain server. Is user authorized to talk?

  7. If nothing obvious, find one sacrifical computer that does not work, reinstall everything and see if that helps.

    Basically something is misconfigured. Now to figure out what.

Question (cont'd):

It had the following in WWWBATCH.INI: 
	[www9x34I]
	Lasterror = 124 (NetUserGetInfo)
At the moment it looks like it might be something to do with the fact MS Office was removed and reinstalled.

I compiled with the 98E. Any ideas?

Answer:

That means invalid level. We call NetUserGetInfo at level 3, which is valid only for NT servers, so the user apparently specified a non-NT server.

It sounds like a network interface problem talking to the NT server. First, make sure the server being specified is really an NT machine, not a Win95 machine. The other reason this might fail is if the NT server is a nonstandard configuration, such as NT running Citrix Winframe, so that it is not "acting" like an NT server.

Second, compare the copies of RADMIN32.DLL and RLOCAL32.DLL with the ones on the machines that work, and replace if necessary. RLOCAL32.DLL is involved in the remote calls, so try replacing that on the problem machine with a copy from one of the good machines. The NetUserGetInfo function is in RADMIN32.DLL, which is the DLL we make a call to in that function.

Other than that, it could be pretty much anything installed (or not installed) on the bad machine that makes it behave differently. I would start by looking at the installed network components (drivers and protocols).

Do any other w9x functions work from that machine?

Question (cont'd):

Strange. As the same code works fine on another PC. In fact it does seem to be related to the fact that MS Office was removed and re-installed.

When going back to an older build the script will run fine, then when Office is removed then reinstalled the script will fail.

The problem is that Office is not that stable on the build which was why it was being removed and reinstalled :)

The server that it is trying to connect to is there. :)

Answer:

EEEK. Looks like you are facing the all too common "uninstall" bug wherein the uninstall routine for various products do not do exactly what they are supposed to.

My condolences. Reinstall windows ? Or at least fix a damaged windows installation? (see more below)

Question (cont'd):

I was expecting that reply :) I just had a vain hope that we'd be able to track down the problem.

For the moment we have just tried to patch Office up to the latest SP. We are looking at moving to NT in the near future so will try to limp along without rebuilding the build from scratch for the moment.

Thanks for the help :)

*** MORE INFORMATION PASSED ON BY A USER ***

IF you are still having a problem with all 9x functions receiving Winbatch 531 errors...

Try Opening User manager, Do you get an error????? if so.....

Two system dll's (namely rpcrt4 & rpcltc1) need to be the same version. During some update, one gets reverted to an older version and bam!, wbt error 531! In addition, these affected machines also cannot run the W95 version of User Manager. Please refer to the following Microsoft article Q242935. We found that just replacing the (2) dll files with a set from a good workstation worked just fine. 

Article ID:   W13520

Filename:   531 Error with Various Network Functions.txt
File Created: 2001:03:01:14:25:04
Last Updated: 2001:03:01:14:25:04