pmollica

Follow up information: I reviewed my System Log on the affected machine. System File Checker when it ran complained about not being able to replace plugin.ocx in the System32 folder. However, when I run a search for that file now, it only shows up on C:\WINDOWS\ServicePackFiles\i386. It does not show up in any other place on the Hard drive. I did some research on that file, and it appears to be some sort of shim for Internet Explorer compatibility. On my next install (this week), if I have the same problem, I will simply delete that file and see if the error goes away prior to reinstalling the Service Pack 1.

Follow up information: I reviewed my System Log on the affected machine. System File Checker when it ran complained about not being able to replace plugin.ocx in the System32 folder. However, when I run a search for that file now, it only shows up on C:\WINDOWS\ServicePackFiles\i386. It does not show up in any other place on the Hard drive. I did some research on that file, and it appears to be some sort of shim for Internet Explorer compatibility. On my next install (this week), if I have the same problem, I will simply delete that file and see if the error goes away prior to reinstalling the Service Pack 1.

Thanks, perhaps I wasn't clear. I solved the immediate problem by re-installing service pack 1. Now my backup is working fine. And since I didn't remove anything when I created the Nlite image, what I'm trying to determine is what exactly is being corrupted and why when installing from the Nlite image CD. Symantec says every one of these they've seen was from an NLite install. Seems like a bug in NLite, perhaps?

Symantec Backup Exec 10d fails on system state backup on MS Windows Small Business Server 2003. After troubleshooting the problem with Symantec 2nd Tier Support, we determined that re-installing Windows Server 2003 Service Pack 1 fixes the problem. Apparently, there are a couple of corrupted files in the System32 folder, one of which is plugin.ocx which cause the problem. Running SFC did not fix it, it said it couldn't overwrite the files in question. Symantec rep says he's seen dozens of them, and the only thing in common was the original install was done from an Nlite CD. Any help appreciated!

I can't tell you how it happens, but I can tell you that if you reinstall Windows Server 2003 service pack 1, it fixes the problem. Apparently, there are a couple of corrupted files in the System32 folder, one of which is plugin.ocx which cause the problem. Running SFC did not fix it, it said it couldn't overwrite the files in question. I worked with a Symantec Advanced Support Rep, and he says he's seen dozens of them, and the only thing in common was the original install was done from an Nlite CD. That's why I'm here, trying to find a solution.

I can't tell you how it happens, but I can tell you that if you reinstall Windows Server 2003 service pack 1, it fixes the problem. Apparently, there are a couple of corrupted files in the System32 folder, one of which is plugin.ocx which cause the problem. Running SFC did not fix it, it said it couldn't overwrite the files in question. I worked with a Symantec Advanced Support Rep, and he says he's seen dozens of them, and the only thing in common was the original install was done from an Nlite CD. That's why I'm here, trying to find a solution.