info on prpcui.exe

trying to get rid of Apropos.exe -Embedding but having trouble

you need SpyBot !! this little freak found 26 more bad things after ad aware said the system was clean

The operation failed because:
Failed finding a sutable domain controller for the domain MYDOMAIN.local "The specified domain either does not exist or could not be contacted."

329860 - "Replication Access Was Denied" Error Messages Occur After You Promote a Server to Domain Controller

Event Type:	Error
Event Source:	SAM
Event Category:	None
Event ID:	16650
Date:		12/18/2003
Time:		5:50:36 PM
User:		N/A
Computer:	MYSERVER
Description:
The account-identifier allocator failed to initialize properly. The record 
data contains the NT error code that caused the failure. Windows 2000 will 
retry the initialization until it succeeds; until that time, account 
creation will be denied on this Domain Controller. Please look for other 
SAM event logs that may indicate the exact reason for the failure.
Data:
0000: c00000dc


Event Type:	Error
Event Source:	NETLOGON
Event Category:	None
Event ID:	5721
Date:		12/18/2003
Time:		5:38:36 PM
User:		N/A
Computer:	MYSERVER
Description:
The session setup to the Windows NT or Windows 2000 Domain Controller 
 for the domain MYDOMAIN failed because the Domain Controller 
does not have an account for the computer MYSERVER.
Data:
0000: c000018b


Event Type:	Error
Event Source:	NETLOGON
Event Category:	None
Event ID:	5721
Date:		12/18/2003
Time:		5:33:52 PM
User:		N/A
Computer:	MYSERVER
Description:
The session setup to the Windows NT or Windows 2000 Domain 
Controller \\server.MYDOMAIN.local for the domain MYDOMAIN failed 
because the Domain Controller does not have an account for the 
computer MYSERVER.
Data:
0000: c000018b

ipconfig /registerdns

be sure to have DNS configured correctly .. including reverse lookup zones !!

Symantec tech support has no clue what causes this error, but I used the following solution:

Create a "c:\tech" folder and use this command "subst z: c:\tech" to fake out the installation. For some reason "Z:\MyDocs\My Pictures\Sample Pictures.lnk" is created. This is what crashes the installation.

 

 

( Symantec Internet installation Win98 Windows 98 2003 2004 )

Check to make sure the "System" user has full control of the root directory. I also noticed the "Task Scheduler" service won't start if this isn't correct.

 

 

( Win2K )

The file it was looking for is:
C:\Windows\Temporary Internet Files\RPTDATA.DAT

Apparently, there is no fix for this. Even though all configuration files were correct, the program gets confused at random and decides to complain that there's no data in the temp internet files directory. I upgraded the thing to Windows XP and the issue went away. We did have to set up compatible laser printer drivers in addition to the proper ones.

 

 

( WinME )

I don't know exactly what you would classify this as, but it occurs while "Wininit.exe" is processing the "Wininet.ini" file just before Windows actually loads. Another little error that has very little posted about it. The text reads as follows:

===   ===   ===   ===   ===   ===   ===   

Windows could not upgrade the file %1 from %2
%1: %2
Windows could not upgrade one or more system files before starting.
Windows may not start or run properly.

If Windows fails to start, run SETUP again.

===   ===   ===   ===   ===   ===   ===   

I suspected the Windows installer may be at fault, so I downloaded and installed the current version. Reboot, there's the error again. Then I ran through reinstalling WinME using it's setup.exe program. During setup, this error showed up quite a bit. As a last resort, I applied the Windows Installer once more and *boom* it's fixed :)

 

 

( WinME )

I was trying to install Microsoft's .Net smack and ran into a strange error with the Windows Installer service. After failing miserably at locating any information on the trouble, I stumbled across two interesting documents. One mentioned several manual steps which end up rolling back the installer to version 1.1 in order to install software .. then reinstalling the later version back on the system.

The fix was to perform the following two commands either in a command prompt window or from the run line:

MSIEXEC /unreg
MSIEXEC /regserver

worked like a charm !

 

 

( Win2K )