Runtime Error! Program: C:...

Forum|Forum|17 years ago
May 7, 2009
4 replies
4118 views

Hi all,

I just finished installing Robohelp 7 onto my Vista box for the first time. After entering the license and proceeding it error'd out. I'm able to go into Robohelp HTML and RoboSource Control 3 Explorer, but when I try to open Robohelp for Word I get the following error popup. Anyone seen this before and can help me troubleshoot?

OS=Vista fully patched.

Word=Office 2007 Pro fully patched.

The popup is:

Titled Microsoft Visual C + + Runtime Library

Red X Runtime Error!

Program: C:...

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information.

OK button.

Thanks.

RH for Word

This topic is closed to new replies. Start a new post to keep the conversation going.

T

Theodorakis55

Participating Frequently

I had the same issue. It was a bad link on 2 document. Deleted the links and it converted very nicely from X5 to RH9 (what is really RH 8 for Word)

W

WriteGuy1960

Participant

I'm having the EXACT same issue.

The curious thing is that RoboHelp for Word 7 used to work with Microsoft Word 2007 on my system.

I did install an application called "Classic Menu for Office" which is an add-in tool that emulates the pull down menu to look like Office 2003.

I'm wondering if somehow this messed up the tags that RoboHelp 7 for Word is looking for?

~WriteGuy~

John_Meidl

Inspiring

We tech writers at this company are experiencing a similar problem. We're testing a PC with Windows 7 on it. We've asked our computer support person to install RoboHelp 8 (including RoboHelp for Word), so that we can verify that both RoboHelp HTML and RoboHelp for Word work correctly before we allow our PCs to upgraded from Windows XP to Windows 7. When we try to open RoboHelp for Word on this Windows 7 PC, a "Microsoft Visual C + + Runtime Library" error appears; here is part of it:

"This application has requested the Runtime to terminate it in an unusual way."

Thanks for any insights or tips!

M

MobdudeAuthor

Participant

Well I sorta figured it out. I installed the app using my user account which is only a local admin id. This is the account that gets the error. When I attempt to run the app using my domain admin account it works no problem. I'm not sure where yet but obviously it's a security rights thingy/issue.

Toodles.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.