Msxml 6.0 Parser Error 1316
Contents |
index The team • Delete all board
Error 1316 The Specified Account Already Exists Vmware
cookies • All times are UTC + 1 hour [ DST ] Forum powered by phpBB © phpBB Group By any use of this Website, you agree to be bound by these Policies and Terms of Use Get OpenOffice
Question Need help? Post your question and get tips & solutions from a community of 418,595 IT Pros & Developers. It's quick & easy. Access 2003 MDE/Install problem (accessrt.cab) P: n/a PW I have a client who decided to Add/Remove Programs
Installshield Error 1316 The Specified Account Already Exists
that haven't been used. Besides Microsoft Works 2002, I'm not sure what else she removed. error 1316 uninstall When she opens up our Access 2003 MDE application, she receives the message "Please wait while Windows configures MS Office Access 2003 Runtime". Then razer synapse error 1316 she gets the error 1311: Source file not found c:\windows\installer\accessrt.cab, verify that the file exists. The file does not exist, so I had her insert the original installation CD and she copied/pasted accessrt.cab from the CD into her c:\windows\installer https://forum.openoffice.org/en/forum/viewtopic.php?f=15&t=69674 folder. Now she opens up the application again. She again receives the message "Please wait while Windows configures MS Office Access2003 Runtime", but this time the hourglass disappears without error 1311. Unfortunately, the application does not open up. She just sees the message, sees the hourglass, and sees the hourglass disappear. She reboots her computer but still same results as in paragraph 2. The next thing we tried was a complete uninstall, but now she gets the error 1316: https://bytes.com/topic/access/answers/810775-access-2003-mde-install-problem-accessrt-cab Setup can not read from file d:\files\13d25c.msi, check connection to network or CD drive. I've never heard of this .msi file. Any ideas? Jun 27 '08 #1 Post Reply Share this Question 1 Reply P: n/a PW Here is what the client did: When I went in to System Restore for Sunday it had a list of the things that I removed. Here's what I wasn't sure about that could be the culprit: Compatibility Pack for the 2007 Office System Microsoft Office Access 2003 Run time (but it shows to be there in the add or remove list?) MSXML 4.0 SP2 MSXML 4.0 SP2 Parser & SDK MSXML 6.0 Parser These were removed but later I reinstalled them when I realized there wasn't a more recent version: Microsoft Word 2002 Microsoft Works Suite Add-in for Microsoft Word *-------- On Wed, 18 Jun 2008 09:43:16 -0600, PW
in 'ESET NOD32 Antivirus' started by rpremuz, Mar 27, 2009. Thread Status: Not open for further replies. rpremuz Registered Member Joined: http://www.wilderssecurity.com/threads/nod32-v4-installation-problems-and-teatimer-spybot-r-d.237386/ Jan 18, 2005 Posts: 100 Location: Croatia While trying to upgrade the NOD32 Antivirus Business Edition from ver. 3.0.684 to ver. 4.0.314 on a MS Windows XP Pro. SP3 I've got the following error (logged in the einstaller.log file): Status 1012, ID 0: Failure during the package install - exit code: 1603, description: Fatal error during installation. The error 1316 installation was done using the ESET RAC ver. 3.0.105. Upgrade by running the eavbe_nt32_enu.msi directly on the Windows was also unsuccessful: the installer reported the error and rolled back its job. I also noticed that the following error was logged in the Windows Application Event Log: Event Type: Error Event Source: MsiInstaller Event Category: None Event ID: 11316 Description: account already exists Product: ESET NOD32 Antivirus -- Error 1316. A network error occurred while attempting to read from the file: C:\WINDOWS\Installer\setup.msi Then I realized that the TeaTimer resident program (part of the Spybot - Search & Destroy) was started on that Windows. I uninstalled the Spybot-R&D, restarted the Windows and tried to upgrade to ver. 4.0.314 but the same errors happened again. I also tried to uninstall NOD32 3.0 but exactly the same errors happened again. So the only solution was to restart the Windows in safe mode, delete the NOD32's info from the System Registry and its files from the system partition: C:\Program Files\Eset C:\Documents and Settings\All Users\Application Data\ESET After that I successfully installed the NOD32 AV BE ver. 4.0.314 using the ESET RAC. A post festum question: is it possible that the TeaTimer creates problems to the NOD32 installer? I ask that as the upgrade from NOD32 v3 to NOD32 v4 was successful on another 50 MS Windows XP Pro. SP3 machines in the LAN and some of them had the Spybot-R&D installed, even with