Administrative Templates Error 51 Unexpected keyword

Asked By 10 points N/A Posted on -
qa-featured

I download one template from the internet and install it at my localhost server.

When I install that template then some part of template appear but some part of template not appear here comes winexit.adm error.

I don’t know can I remove this error is this error due to Code or some template file missing error.

Administrative Tamplates

The following error occurred in

\montage.localsysvoimontage.localpolicies{31B2F340 -016D-11D2-945F-00C04FB984F9}Adminwinexit.adm on line 59:

Error 51 Unexpected keywork

Found: CATEGOR

Expected: CATEGORY

The file can not be loaded.

OK

SHARE
Best Answer by jacks.niccoli59
Best Answer
Best Answer
Answered By 0 points N/A #96491

Administrative Templates Error 51 Unexpected keyword

qa-featured

Hi Liz,

Administrative Templates

The following error occurred in

\montage.localsysvoimontage.localpolicies{31B2F340 -016D-11D2-945F-00C04FB984F9}Adminwinexit.adm on line 59:

Error 51 Unexpected keyword

Found: CATEGOR

Expected: CATEGORY

The file can not be loaded.

As you see in your error message box. Then analyze your problem. For me your problem was in your document of file name or something like that. As you see “unexpected keyword” so it means there is something wrong in your key word. Go back to your key word and find out what was wrong with that. And put the right keyword in your application then try it again. Just put the right keyword. That’s it.

I hope they would help.

Thanks

Answered By 5 points N/A #96492

Administrative Templates Error 51 Unexpected keyword

qa-featured

The Error 51 is starting that it is finding an issue with the ADM file, may be corruption or XP SP2 was installed and then group policy edited from that machine. If it was edited it could have updated the inetres.adm  file which has some expanded explanation that is too long for 2000 machines to handle.

There is a hotfix available 842933 that is not in a public article yet but that can be applied to Windows 2000 machines to correct that error. If you wanted the hotfix you would need to contact Microsoft.

Or the other option would be to revert the inetres.adm file to a previous version of the file from a Windows 2000 machine with the latest SP installed.

Related Questions