Our main server seems to be having trouble.

Trying to register some dlls, it doesn't like it, but does on other servers.

Tried sP4 but it failed during install, going to try and re-install sp3 tonight to give the machine a refresh. Lets hope it doesn't bomb out!

Anyone have an utils that can inspect the server setup, and see if anything is wrong with it? Been looking through event viewer but nothing is coming up - quite annoying!!

help us out a bit.. what do you want to check..


Whats playing up and what are the dlls?

David

David - I would if I could, but nothing more to say on it.

I can manually register the dll's on another server, just not on this one.

I will put the error message 0x... on tomorrow - but have already looked in technet, and it reckons it is down to not correct permissions, but have already checked and they are.

unregister dll.. delete dll... chkdsk.. reboot..

regsvr32 dll..

corrupt registry / disk?

run regsvr32.exe dllname.dll and gimme error msg..

corrupt dll..??

David

Depending on the amount of installation time and work you will have to put into it, it may be worth carrying out a fresh installation of Win2k Server and applying the latest service pack straight off :)

Project STI: that isn't an option I am afriad :)

unregister dll works fine, when registering the dll it comes up with:

DllRegisterServer in winsec.dll failed. Return code was: 0x80020009

I can register the same dll on a diff server/machine - it is a problem on this server.

One of my colleagues tried to reapply service pack 3 last night, but it came up with access denied. Even though logged in as domain admin. Which is a bit of a bugger - something is screwed - wonder if it is the registry.


[Edited by ChristianR - 7/17/2003 8:10:52 AM]

I'm affraid thats a generic "There was an error" error code :rolleyes: have you tried viewing the dependencies? see what other dll's it relies on? sometimes the order which you register them can effect it too...

also try forming a circle around the server (holding hands) and chanting "work work work" tends to help :D

Have been speaking to the people who wrote it, and they are also stuck. Since the dll works on another server as well, so not a problem with the dll.

Deff something major wrong with it, has never quite been the same since backup exec almost killed it last year.

Since sp3 can't re-apply any more on it - something serious somewhere going wrong.

May try the circle thing :)

Does anyone know of a program that I can run before running the sp that will track what files are being called etc? so I can try and diag what is causing it to go pete tong?

If TechNet says it's down to permissions, maybe it means registry permissions? Have you checked the security on the areas of the registry that it's trying to write to?

If VBE almost blew the server up last year, then IMO you're fighting a losing battle.

Bite the bullet and start planning a rebuild or server substitution.

Chris.

The DLL may fail to register due to a missing dependancy. Use Depends.exe to see what it relies on

Christian

Try resetting Server permissions back to default, then try the dll's again

Steve