Microsoft Visual C++ Runtime Library Runtime ERROR!

[TryingTo_Learn01]

Installed trial version InDesign CS5 with update patch 7.0.4 on a clean/new installation of Windows XP Pro Sp3.

- InDesign CS5 Trial was the first program installation on the drive.

- Unable to run due to following:Runtime Error! Program C:\.....InDesign.exe The aplication has requested the Runtime to terminate it in an unusual way.  Please contact the application's support team for more information.

I called tech support; however, they will not provide assistance on trial products.

Any assistance is appreciated.

[TryingTo_Learn01]

Over zealous - guilty!

I did not have a printer installed at the first installation; however, during yesterday's successful installation threre was a local / network printer installed.

[Peter Spier]

Local means attached to the computer, not a network printer. Should probably be on-line, too.

[John Hawkinson]

Should it also have yellow canary #20 paper in it?

Yes, that's a bit sarcastic, but it seems like a crazy amount of hoops. I know there are cases where InDesign has been shown to require a printer connected to work the first time, but I am kind of skeptical that one has to go the whole nine yards. (and we have InDesign and InCopy installed on dozens of machines that have never had a local printer and never will, with no problem; not that that means anything, of course...A thousand people not having a problem doesn't mean the 1 person with the problem is any less legit...)

So anyhow, are we sure that all of these are necessary? Or are they just shots in the dark?

[Peter Spier]

These are things that have been shown to work for some users with similar problem reports. I can't tell you why they work or if they will always work. I"ve never had an installation fail, myself, either, but I do a lot of prep work to make sure there are no conflicts during the install, especailly with CS3 which was notorious for failure at the slightest provocation.

I can't recall for sure if I've ever seen a run-time error like this on my own system, either, but I think I might have, and I either rolled back using System Restore or did a reinstall to fix it. I'm quite sure I've not seen it personally on a first-launch occasion.

[TryingTo_Learn01]

Still no solution in sight; however, somehow my question was marked solved.

[Peter Spier]

The only one who can mark a question as answered is the person making the original post. It's possible marking John's earlier answer as correct also triggered an "answered" status, but I don't think that's automatic.

[TryingTo_Learn01]

Would you advise starting a new post?

[TryingTo_Learn01]

Just called Adobe, "Really sorry sir, we are not authorized to provide support for trial versions.  You must first buy the product to receive support."

My response,"Why would I purchase if I can not activate a trial?"

Adobe response, "I am really sorry - goodbye."

Pathetic!

[Peter Spier]

well, you could go ahead and make the pruchase so you have a serial number and access to free support for installation issues (which this seems to be). If you like it, no harm done. If you don't like it, you have 30 days to return for a refund.

[TryingTo_Learn01]

I respectfully dissent.

One should make a $$$ purchase in hopes of cajoling tech support to resolve a KNOWN issue?

My problem is identical to numerous others, e.g. search Adobe forums "InDesign CS5 runtime error."  Several threads of multiple users, rather "potential" users, precluded from opening the application due to C++ error(s) commencing at "starting up service registry."

Additionally, I posted my questions on Microsoft C++ forums only to receive, "This is an Adobe issue."

Perhaps I am naive but why does Adobe actively refrain from resolving this issue?

[John Hawkinson]

Perhaps I am naive but why does Adobe actively refrain from resolving this issue?

There's a lot going on.

Adobe has made a business decision that they are going to offer free trials to non-customers for free, but not provide support for those free trials. That's a reasonable decision to make. It's especially more reasonable given that they offer refunds to customers who are not satisfied -- it makes sure they do not waste their precious staff resources dealing with people who are not serious but does not raise a high barrier to entry.

As a customer who wants their support to be responsive to me, but is not satisfied with the turnaround times on paid support, I appreciate that they want to not distract their limited support resources with "freeloaders."

I think it is an error to regard this as a "known issue." There are a wide variety of problems that can lead to installation failures, but it is not easy to figure out which they are. In fact, sometimes it is immensely frustrating and takes a lot of support time. If there was a canned easy solution, we would tell you what it was and indeed, there would surely be an Adobe Knowledgebase article that answered definiteively. (There are several kb.adobe.com articles that try to assist with this problem, but it does not seem to solve everything for all people).

I am sure Adobe would love to fix this category of problems. It leads to frustrating for users, people not purchasing the product, wasted support time, etc., etc. That doesn't mean they know what is wrong or how to correct the underlying problem. And in fact, even if they have a series of workarounds for the problem, or can tell you what to do to resolve it, that does not mean that they can integrate those workarounds into their installer and have a product that installs itself perfectly for everyone, all the time. That work may take time, or it may take resources presently unavailable, or there may be big mysteries about how something that ought to work manages to fail.

The situation is unfortunate, but I don't think deserving of condemnation.

You say that your "problem is identical to numerous others." Unfortunately, while you might think that, and it might seem that way, you cannot know that. It might be true, it might not be true. It may appear the same as others, but that is not the same. Identical symptoms may not have identical causes, and installation problems like this are unfortunately quite difficult to address sometimes.

p.s.: I guarantee you won't have Microsoft C++ errors if you install InDesign on a Macintosh 😉

[Peter Spier]

While John should know better than to try to start a platform war, I have to agree with him on most of the other points.

Given that 99.99% of Windows users who try to install the product DON'T see this error, it's quite likely that the issue is some sort of conflict with other software on your system. Since you said all you had was an OS, that means it might be a driver. How would you propose Adobe "fix" this?

Also, you just mentioned "starting up service regitry" at failure. I don't recall you mentioning this before, and it is usally indicative of a probelm in the SING folder or plugin. Searching the knowledgebase for that pharase should take you to the known fixes.

[TryingTo_Learn01]

I have read your and all previous posts re: "starting up service registry" - tried everything to no avail.

[Peter Spier]

I'm not sure what else to tell you. Without being in front of your system I can't dig into it to see what might be the conflict or problem, but I'm quite convinced that whatever it is, it's unique to your configuration.

[John Hawkinson]

I have read your and all previous posts re: "starting up service registry" - tried everything to no avail.

That's not terribly clear.

Have you removed the SING plugin itself?

[TryingTo_Learn01]

First, I renamed the SING folder, e.g. SING.bak, then I removed it to the desktop. I would remove it via InDesign; however, the program has never launched.

The above actions and other suggestions offered by others regarding "starting up service registry" error/failure to launch still crashes the program two seconds after stating "starting up service registry" C++ Error etc., as stated in my initial post.

[John Hawkinson]

That would be a No.

Please try removing SING.RPLN from the InDesign plugins folder.

[TryingTo_Learn01]

I used "Windows search" and removed every occurance of "SING" files and/or folders.

InDesign crashes, Microsoft Visual C++ Library Error message with these error logs:

[TryingTo_Learn01]

[Peter Spier]

The SING plugin is SING.apln and is located in the InDesign program folder under: \Adobe InDesign CS5\Plug-Ins\Text. THere will also be a SING folder in the Adobe Common Files folder. Move them both.

[TryingTo_Learn01]

Thanks!

Earlier today I located both, cut and pasted to desktop. Rebooted and

realized the same C++ runtime error.

Incidentally, I am running two Athlon 2800 MP+ processors.

[Peter Spier]

Just for kicks, turn off video hardware acceleration.

[TryingTo_Learn01]

Same error messages

[Peter Spier]

At this point, I think your best hope is to buy a license, start a tech support case, and get it escalated to someone who can look at your system remotely and try to figure out what the problem is. There's clearly something special about your system.

You metioned AMD chips. I recall a very old bug with some AMD processors, but as far as I know anything produced in the last two years or so should be fine.

[TryingTo_Learn01]

Thank you very much for your time, suggestions and perseverance.

I will not purchase a product with known problems in "hopes" of tech support rectifying issues which may/may not be unique to my system.

Obviously, there are others who experience/have experienced similar issues and Adobe elects to address such on an individual basis. I shall uninstall and take my business elsewhere.

Best regards to all.