Error 1316 Access Runtime
Contents |
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 10 Oct 2016 11:39:08 GMT by s_ac15 (squid/3.5.20)
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help error 1316 the specified account already exists Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor installshield error 1316 account already exists Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error 1316 when removing Access 2003 Runtime Want to Advertise Here?
Error 1316 Account Already Exists Uninstall
Solved Error 1316 when removing Access 2003 Runtime Posted on 2015-07-15 MS Access Windows Server 2008 MS Office 1 Verified Solution 6 Comments 275 Views Last Modified: 2015-08-18 Hi On a Windows 2008 Server, I http://answers.microsoft.com/en-us/msoffice/forum/msoffice_access-mso_winother/access-runtime-installation-error-1316/b306d911-1b9a-4856-a6c1-ab553e2a2c08 have Microsoft Office 2003 Standard installed. Also installed is Access 2003 Runtime. I'm upgrading to Office 2010 Standard, and planning to install Access 2010 Runtime. My first step is to remove Access 2003 Runtime. I've tried this several ways, and it keeps failing: 1) Via Control Panel, Programs and Features, Uninstall 2) Select Control Panel, Programs and Features, Change, then selecting Uninstall from the Access Setup options. 3) Selecting the Access 2003 https://www.experts-exchange.com/questions/28697419/Error-1316-when-removing-Access-2003-Runtime.html Runtime MSI, then selecting Uninstall from the Access Setup options. 4) Installing MS Fixit and letting that uninstall it. The usual fail message is "Error 1316: The specified account already exists" Note that I've tried this on different clones of the original server. Is there some better way of removing it? Could there be possibly some security or Group Policy setting that stops removal of programs. The servers I'm looking at are all terminal servers, so I wonder would there be any setting there that could interfere. Thanks 0 Question by:jdhackett Facebook Twitter LinkedIn Google LVL 12 Active today Best Solution byJohn Tsioumpris Sometimes removing Ms Access 2003 runtime is not an easy task...Probably you have installed Ms Access runtime under a different account and so there are some "problems" when you try to uninstall.... Go to Solution 6 Comments LVL 33 Overall: Level 33 MS Access 32 MS Office 6 Windows Server 2008 1 Message Active 2 days ago Expert Comment by:PatHartman2015-07-15 Since Access full and runtime are BOTH named MSAccess.exe, unless you specifically installed them in separate directories, you probably have only the full version installed. Clearly due to the confusion, I would not recommend installing the runtime if you have the full product for the same version. You can always
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about http://stackoverflow.com/questions/30975371/windows-msi-error-1316-the-specified-account-already-exists hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges https://community.spiceworks.com/topic/1068304-failing-to-uninstall-access-2003-runtime-should-i-use-ms-fixit Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Windows msi: error 1316: the specified account already exists up vote 1 down vote favorite 1 The execution of a wix package from a bundle outputs "error 1316: The error 1316 specified account already exists" during upgrade. How can a windows installer output this error code? I'm afraid there isn't much documentation about it. We previously released a product consisting of a single msi package, and now we are preparing an upgrade which consists of a wix bundle containing a new version of this msi package. The product code and filename between the original msi package and the update haven't changed. Edit: The msi package for now doesn't support account already exists upgrade. When the user needs to upgrade (whenever it's a major upgrade, minor upgrade or small update), he must first manually uninstall the previous package... Edit 2: I just removed the references to util extension for compilation and the installer seems to work fine... I still need to fully test it though. wix windows-installer bundle upgrade share|improve this question edited Jun 23 '15 at 11:41 asked Jun 22 '15 at 8:37 Brainless 5061318 add a comment| 4 Answers 4 active oldest votes up vote 1 down vote An upgrade MSI requires the MSI to have a new ProductCode, an incremented ProductVersion (in the first 3 fields) and the same UpgradeCode. So it's not clear to me that you're actually getting an upgrade, depending on what the Burn part thinks you are doing. It can't do an upgrade because you have the same ProductCode. (You need a MajorUpgrade element in your MSI to do a proper upgrade). So there is some doubt as to whether you're getting an actual full upgrade. If your intent is to replace the installed MSI with a full upgrade, and a higher versioned product then use MajorUpgrade. So Burn may have decided to do an in-place update by reinstalling the MSI file (and that's more like a patch than an update), and that's relevant because you don't say whether you have any custom actions or WiX uti
Upgrade Upgrade a K1000 box to 5.5 and then upgrade and deploy the new agent. Offsite backup Secure, reliable and cost effective offsite backup Setup Cascade servers Setup new Cascade servers TECHNOLOGY IN THIS DISCUSSION Join the Community! Creating your account only takes a few minutes. Join Now Hi I'm trying to remove Access 2003 runtime from a Windows 2008 terminal server. Going to switch to Access 2010 runtime. This is a clone of one of the existing terminal servers, so I'll just delete it and restart if thats required. Using Control Panel, Programs and Features, Uninstall. First time, I got a message that DEP prevented the Uninstall. So I changed the DEP to “Turn on DEP for essential Windows programs and services only”. Then I rebooted and tried again.This time it seemed to succeed. But when I rebooted, the program was still there. So then I googled a bit, and I saw some results that you should the original Access 2003 MSI. So I launched that, took the Uninstall Option. That failed with a message "Error 1316: The specified account already exists." Searching the Microsoft website, I keep getting referred to the Fixit program https://support.microsoft.com/en-us/mats/program_install_and_uninstall?wa=wsignin1.0 The claim on the page is "Automatically repair issues that block program installation or removal because of corrupted registry keys" From what I can tell, you don't get to customise the options, the Fixit tool figures out everything for itself. However, I'm not sure I want to run it. I have to uninstall Access 2003 runtime on 12 production servers. So I'd prefer to know the actual fix, not run the Fixit tool against the production servers. Or am I wrong, is the Fixit tool ok for use in the live environment? I welcome your thoughts on Fixit. Or of course, I'd welcome a solution to the removal problem as well! Thanks Reply Subscribe   9 Replies Chipotle OP Fatbeard Jul 15, 2015 at 11:10 UTC Decided to try the Fixit program on the clone. It failed :( So I guess I won't be trying that on the live servers.... Now what should I do? 0 Mace OP LarryG. Jul 15, 2015 at 2:26 UTC Have you tried, from that MSI, installing it again? That may repair the errors, which might then allow a normal uninstall to work correctly. 0 Chipotle OP Fatbeard Jul 15, 2015 at 3:05 UTC I haven't tried that. I get two options - re-