Re: Microsoft Visual C++ Runtime Library Runtime Error

Dusko, my solution puts a 32-bit executable into the 64-bit \Program Files
directory, which I thought was reserved for 64-bit programs. Is the
acceptable?

"Dusko Savatovic" wrote:

Ron, that's how it works now and how Microsoft arranged things now with
64-bit technology. It's better not to mess with system paths. You found a
good solution so leave it as it is. If you really have to, it would be a
good idea to do modifications for individual scenarios and by using a batch
file that would set the necessary environment variables and invoke the
application. Like I mentioned before, Application Compatibility Toolkit has
a feature for presenting 'fake' environment to apps, so it's worth
investigating if you're preparing for some serious migrations. They call
this 'fake' environment a virtualized environment. What happens is that they
intercept API calls and if the app wants to write to a restricted location
(such as %windir%), a similar folder structure is created inside a user's
profile. Check the Technet site for more info:
http://technet.microsoft.com/en-us/windows/aa905066.aspx


"Ron Sochanski" <RonSochanski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:525FAA21-4A40-496A-ADC4-FE7B4D336961@xxxxxxxxxxxxxxxx
Dusko, any idea as to why the error would occur with the executable
installed
in C:\Program Files (x86) but not when it's installed in C:\Program Files?
Could I perhaps modify the system path so that the error doesn't occur
when
installing in C:\Program Files (x86)?

"Dusko Savatovic" wrote:

Thanks for sharing, Ron

"Ron Sochanski" <RonSochanski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@xxxxxxxxxxxxxxxx
I did not yet try the Application Compatibility Toolkit as you had
suggested.
I did, however, copy the executable from C:\Program Files (x86)\... to
C:\Program Files\... and then ran the executable from there. The error
did
not occur.

"Dusko Savatovic" wrote:

Try to download Application Compatibility Toolkit. It is designed for
Vista,
but since 2008 is designed on the similar base it may help. ACT
contains
so
called 'shims' that can help you set up a 'fake' environment for your
app.
It can also monitor API's used in the app and give you detailed
report.

I suppose you already tried the usual trick with 'Run as
Administrator'
during the app install and launch.



"Ron Sochanski" <RonSochanski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@xxxxxxxxxxxxxxxx
The application in question is 32-bit and was developed with Visual
C++
6.0.
Please correct me if I'm wrong, but I don't think that the 64-bit
Visual
C++
2008 redistributable would help, since it's for 64-bit Visual C++
2008
applications.

"Dusko Savatovic" wrote:

How about downloading and installing
Microsoft Visual C++ 2008 Redistributable Package (x64)

The URL may wrap
http://www.microsoft.com/downloads/details.aspx?familyid=BD2A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en


"Ron Sochanski" <RonSochanski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:B662044C-74FF-4B83-A062-276CC5C55920@xxxxxxxxxxxxxxxx
Hello. I have a 32-bit MFC application that runs fine on Windows
Server
2003
Standard Edition SP2. However, when I try to run it on Windows
Server
2003
R2 Standard x64 Edition SP2, I get the following error message:

Microsoft Visual C++ Runtime Library
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.

I tried to apply the hotfix described in KB916177, only to find
that
Windows
Server 2003 R2 Standard x64 Edition SP2 already contains the fix.

Any help with fixing this error would be greatly appreciated.
Thank
you.








.

Relevant Pages

  • Re: Microsoft Visual C++ Runtime Library Runtime Error
    ... It's better not to mess with system paths. ... it would be a good idea to do modifications for individual scenarios and by using a batch file that would set the necessary environment variables and invoke the application. ... What happens is that they intercept API calls and if the app wants to write to a restricted location, a similar folder structure is created inside a user's profile. ... installing in C:\Program Files? ...
    (microsoft.public.windows.server.general)
  • Re: Microsoft Visual C++ Runtime Library Runtime Error
    ... coded for '\Program Files' instead of %ProgramFiles%. ... ie it's unlikely that another 64-bit app will reference the same component ... file that would set the necessary environment variables and invoke the ... installing in C:\Program Files? ...
    (microsoft.public.windows.server.general)
  • Re: Microsoft Visual C++ Runtime Library Runtime Error
    ... I have modified the app to use ... %ProgramFiles% instead and my problem has been solved. ... file that would set the necessary environment variables and invoke the ... installing in C:\Program Files? ...
    (microsoft.public.windows.server.general)
  • Re: Some personal linux observations
    ... One of my big bitches about the M$ environment is that the command line ... but open source developers are usually more interested in expressing ... installing software from sourcecode. ...
    (alt.os.linux)
  • Re: In need of 5 TS connections
    ... But if there are no unused workstations, the cost of installing ... If the ts is set up to host the user desktops, and the app is installed on ... >>> only thing I had to do was add the TS licensing ...
    (microsoft.public.windows.server.sbs)