eventvwr.msc is not a valid win32 application.

[Guest TampaWebDevelopment@gmail.com]

I installed Symantec Corporate on my Windows Server 2003 Standard SP2.

After some updates, I rebooted the server. As soon as I would login,

it would immediately log me out. I read somewhere that I needed to

copy a good copy of userinit.exe to the server's C:\WINDOWS\system32

directory as wsaupdater.exe. I did and tried to login. No luck. I

noticed that almost as soon as I finished copying the file to the

servers system32 directory, the file was changed by "something"

because the file size changed. So, I fired open services.msc on my

workstation, which is on the same network as the server with the

problem. From the services panel, I connected to the server with the

problem and changed all the Symantec services to disabled. I typed

"iisreset /reboot servername" from the command line and rebooted the

server. When it came back online, I copied the userinit.exe and

wsaupdater.exe to the server's system32 directory. I was then able to

login.

 

OK. So, I am now logged in and I want to look at the Event Viewer to

see if I can see any obvious issues. I click the icon and get the

following error. "C:\WINDOWS\system32\eventvwr.msc is not a valid

win32 application."

 

I tried to copy that file over just like I did the other two files and

it didn't work.

 

Ideas?

[Guest Pegasus \(MVP\)]

Re: eventvwr.msc is not a valid win32 application.

 

 

<TampaWebDevelopment@gmail.com> wrote in message

news:1186741364.209459.246510@x35g2000prf.googlegroups.com...

>I installed Symantec Corporate on my Windows Server 2003 Standard SP2.

> After some updates, I rebooted the server. As soon as I would login,

> it would immediately log me out. I read somewhere that I needed to

> copy a good copy of userinit.exe to the server's C:\WINDOWS\system32

> directory as wsaupdater.exe. I did and tried to login. No luck. I

> noticed that almost as soon as I finished copying the file to the

> servers system32 directory, the file was changed by "something"

> because the file size changed. So, I fired open services.msc on my

> workstation, which is on the same network as the server with the

> problem. From the services panel, I connected to the server with the

> problem and changed all the Symantec services to disabled. I typed

> "iisreset /reboot servername" from the command line and rebooted the

> server. When it came back online, I copied the userinit.exe and

> wsaupdater.exe to the server's system32 directory. I was then able to

> login.

>

> OK. So, I am now logged in and I want to look at the Event Viewer to

> see if I can see any obvious issues. I click the icon and get the

> following error. "C:\WINDOWS\system32\eventvwr.msc is not a valid

> win32 application."

>

> I tried to copy that file over just like I did the other two files and

> it didn't work.

>

> Ideas?

>

 

Try running eventvwr.exe instead. If this does not work, restore

the two files.

[Guest TampaWebDevelopment@gmail.com]

Re: eventvwr.msc is not a valid win32 application.

 

On Aug 10, 6:32 am, "Pegasus \(MVP\)" <I....@fly.com> wrote:

> <TampaWebDevelopm...@gmail.com> wrote in message

>

> news:1186741364.209459.246510@x35g2000prf.googlegroups.com...

>

>

>

>

>

> >I installed Symantec Corporate on my Windows Server 2003 Standard SP2.

> > After some updates, I rebooted the server. As soon as I would login,

> > it would immediately log me out. I read somewhere that I needed to

> > copy a good copy of userinit.exe to the server's C:\WINDOWS\system32

> > directory as wsaupdater.exe. I did and tried to login. No luck. I

> > noticed that almost as soon as I finished copying the file to the

> > servers system32 directory, the file was changed by "something"

> > because the file size changed. So, I fired open services.msc on my

> > workstation, which is on the same network as the server with the

> > problem. From the services panel, I connected to the server with the

> > problem and changed all the Symantec services to disabled. I typed

> > "iisreset /reboot servername" from the command line and rebooted the

> > server. When it came back online, I copied the userinit.exe and

> > wsaupdater.exe to the server's system32 directory. I was then able to

> > login.

>

> > OK. So, I am now logged in and I want to look at the Event Viewer to

> > see if I can see any obvious issues. I click the icon and get the

> > following error. "C:\WINDOWS\system32\eventvwr.msc is not a valid

> > win32 application."

>

> > I tried to copy that file over just like I did the other two files and

> > it didn't work.

>

> > Ideas?

>

> Try running eventvwr.exe instead. If this does not work, restore

> the two files.- Hide quoted text -

>

> - Show quoted text -

 

I get the error Microsoft Management Console cannot be started. Re-run

Microsoft Windows Setup.

 

Error Code: main.cxx 214 800700c1

 

I guess this is more than just the Event Viewer. The problem is that

the server is at a datacenter and not local. Hmmm. I do have the

Windows CD on the server. Do I just need to run the Windows Setup and

choose repair or something?

[Guest Pegasus \(MVP\)]

Re: eventvwr.msc is not a valid win32 application.

 

 

<TampaWebDevelopment@gmail.com> wrote in message

news:1186744309.058672.203750@j4g2000prf.googlegroups.com...

> On Aug 10, 6:32 am, "Pegasus \(MVP\)" <I....@fly.com> wrote:

>> <TampaWebDevelopm...@gmail.com> wrote in message

>>

>> news:1186741364.209459.246510@x35g2000prf.googlegroups.com...

>>

>>

>>

>>

>>

>> >I installed Symantec Corporate on my Windows Server 2003 Standard SP2.

>> > After some updates, I rebooted the server. As soon as I would login,

>> > it would immediately log me out. I read somewhere that I needed to

>> > copy a good copy of userinit.exe to the server's C:\WINDOWS\system32

>> > directory as wsaupdater.exe. I did and tried to login. No luck. I

>> > noticed that almost as soon as I finished copying the file to the

>> > servers system32 directory, the file was changed by "something"

>> > because the file size changed. So, I fired open services.msc on my

>> > workstation, which is on the same network as the server with the

>> > problem. From the services panel, I connected to the server with the

>> > problem and changed all the Symantec services to disabled. I typed

>> > "iisreset /reboot servername" from the command line and rebooted the

>> > server. When it came back online, I copied the userinit.exe and

>> > wsaupdater.exe to the server's system32 directory. I was then able to

>> > login.

>>

>> > OK. So, I am now logged in and I want to look at the Event Viewer to

>> > see if I can see any obvious issues. I click the icon and get the

>> > following error. "C:\WINDOWS\system32\eventvwr.msc is not a valid

>> > win32 application."

>>

>> > I tried to copy that file over just like I did the other two files and

>> > it didn't work.

>>

>> > Ideas?

>>

>> Try running eventvwr.exe instead. If this does not work, restore

>> the two files.- Hide quoted text -

>>

>> - Show quoted text -

>

> I get the error Microsoft Management Console cannot be started. Re-run

> Microsoft Windows Setup.

>

> Error Code: main.cxx 214 800700c1

>

> I guess this is more than just the Event Viewer. The problem is that

> the server is at a datacenter and not local. Hmmm. I do have the

> Windows CD on the server. Do I just need to run the Windows Setup and

> choose repair or something?

>

 

When it comes to repairing servers I'm always conscious of

the high availability that users expect and the large amount of

time I need to spend on rebuilding it. I therefore follow this

path:

- Create a clone disk.

- Test the clone disk.

- Attempt to repair the installation on the original disk.