Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Windows Server General Help » Microsoft Visual C++ Runtime Library Runtime Error
Microsoft Visual C++ Runtime Library Runtime Error [message #164256] Thu, 18 June 2009 15:37 Go to next message
Ron Sochanski  is currently offline Ron Sochanski
Messages: 10
Registered: August 2009
Junior Member
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.
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164279 is a reply to message #164256] Fri, 19 June 2009 03:32 Go to previous messageGo to next message
Dusko Savatovic  is currently offline Dusko Savatovic  Croatia
Messages: 323
Registered: July 2009
Senior Member
How about downloading and installing
Microsoft Visual C++ 2008 Redistributable Package (x64)

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


"Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
> 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.
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164287 is a reply to message #164279] Fri, 19 June 2009 09:10 Go to previous messageGo to next message
Ron Sochanski  is currently offline Ron Sochanski
Messages: 10
Registered: August 2009
Junior Member
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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
>
>
> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
> > 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.
>
>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164290 is a reply to message #164287] Fri, 19 June 2009 11:06 Go to previous messageGo to next message
Dusko Savatovic  is currently offline Dusko Savatovic  Croatia
Messages: 323
Registered: July 2009
Senior Member
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@discussions.microsoft.com> wrote in message
news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
> 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
>>
>>
>> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
>> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
>> > 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.
>>
>>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164303 is a reply to message #164290] Fri, 19 June 2009 13:45 Go to previous messageGo to next message
Ron Sochanski  is currently offline Ron Sochanski
Messages: 10
Registered: August 2009
Junior Member
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@discussions.microsoft.com> wrote in message
> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
> >>
> >>
> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
> >> > 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.
> >>
> >>
>
>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164304 is a reply to message #164303] Fri, 19 June 2009 14:33 Go to previous messageGo to next message
Dusko Savatovic  is currently offline Dusko Savatovic  Croatia
Messages: 323
Registered: July 2009
Senior Member
Thanks for sharing, Ron

"Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@microsoft.com...
>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@discussions.microsoft.com> wrote in message
>> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
>> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
>> >>
>> >>
>> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in
>> >> message
>> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
>> >> > 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.
>> >>
>> >>
>>
>>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164305 is a reply to message #164304] Fri, 19 June 2009 14:49 Go to previous messageGo to next message
Ron Sochanski  is currently offline Ron Sochanski
Messages: 10
Registered: August 2009
Junior Member
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@discussions.microsoft.com> wrote in message
> news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@microsoft.com...
> >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@discussions.microsoft.com> wrote in message
> >> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
> >> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
> >> >>
> >> >>
> >> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
> >> >> > 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.
> >> >>
> >> >>
> >>
> >>
>
>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164313 is a reply to message #164305] Fri, 19 June 2009 16:01 Go to previous messageGo to next message
Ron Sochanski  is currently offline Ron Sochanski
Messages: 10
Registered: August 2009
Junior Member
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@discussions.microsoft.com> wrote in message
> news:525FAA21-4A40-496A-ADC4-FE7B4D336961@microsoft.com...
> > 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@discussions.microsoft.com> wrote in message
> >> news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@microsoft.com...
> >> >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@discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
> >> >> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
> >> >> >>
> >> >> >>
> >> >> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
> >> >> >> > 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.
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >>
> >>
>
>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164314 is a reply to message #164305] Fri, 19 June 2009 15:47 Go to previous messageGo to next message
Dusko Savatovic  is currently offline Dusko Savatovic  Croatia
Messages: 323
Registered: July 2009
Senior Member
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@discussions.microsoft.com> wrote in message
news:525FAA21-4A40-496A-ADC4-FE7B4D336961@microsoft.com...
> 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@discussions.microsoft.com> wrote in message
>> news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@microsoft.com...
>> >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@discussions.microsoft.com> wrote in
>> >> message
>> >> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
>> >> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
>> >> >>
>> >> >>
>> >> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
>> >> >> > 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.
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164317 is a reply to message #164313] Fri, 19 June 2009 16:31 Go to previous messageGo to next message
Dusko Savatovic  is currently offline Dusko Savatovic  Croatia
Messages: 323
Registered: July 2009
Senior Member
Ron, your case is exception to the rule. It seems that your app is hard
coded for '\Program Files' instead of %ProgramFiles%. Besides, it was made
with Visual C++ 6.0. IIRC Visual C++ 6.0 did not create 64-bit apps. So
there's no danger of mixing 32-bit and 64-bit components of that same name
ie it's unlikely that another 64-bit app will reference the same component
(only it's 64-bit version), but get the 32-bit version instead.


"Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
news:B65518F9-E857-4E15-AAC8-32F72F34B2BD@microsoft.com...
> 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@discussions.microsoft.com> wrote in message
>> news:525FAA21-4A40-496A-ADC4-FE7B4D336961@microsoft.com...
>> > 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@discussions.microsoft.com> wrote in
>> >> message
>> >> news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@microsoft.com...
>> >> >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@discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
>> >> >> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
>> >> >> >>
>> >> >> >>
>> >> >> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote
>> >> >> >> in
>> >> >> >> message
>> >> >> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
>> >> >> >> > 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.
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164320 is a reply to message #164317] Fri, 19 June 2009 17:25 Go to previous messageGo to next message
Ron Sochanski  is currently offline Ron Sochanski
Messages: 10
Registered: August 2009
Junior Member
Dusko, I'm not sure what you mean by "mixing 32-bit and 64-bit components".
Could you please explain. Thank you.

"Dusko Savatovic" wrote:

> Ron, your case is exception to the rule. It seems that your app is hard
> coded for '\Program Files' instead of %ProgramFiles%. Besides, it was made
> with Visual C++ 6.0. IIRC Visual C++ 6.0 did not create 64-bit apps. So
> there's no danger of mixing 32-bit and 64-bit components of that same name
> ie it's unlikely that another 64-bit app will reference the same component
> (only it's 64-bit version), but get the 32-bit version instead.
>
>
> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
> news:B65518F9-E857-4E15-AAC8-32F72F34B2BD@microsoft.com...
> > 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@discussions.microsoft.com> wrote in message
> >> news:525FAA21-4A40-496A-ADC4-FE7B4D336961@microsoft.com...
> >> > 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@discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@microsoft.com...
> >> >> >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@discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
> >> >> >> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
> >> >> >> >>
> >> >> >> >>
> >> >> >> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote
> >> >> >> >> in
> >> >> >> >> message
> >> >> >> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
> >> >> >> >> > 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.
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >>
> >>
>
>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164321 is a reply to message #164256] Fri, 19 June 2009 18:44 Go to previous messageGo to next message
Peter Foldes  is currently offline Peter Foldes  Canada
Messages: 1900
Registered: July 2009
Senior Member
The Google Toolbar is the culprit on this one. Uninstall it and reboot and then
re-install

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
> 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.
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164322 is a reply to message #164320] Fri, 19 June 2009 18:26 Go to previous messageGo to next message
Dusko Savatovic  is currently offline Dusko Savatovic  Croatia
Messages: 323
Registered: July 2009
Senior Member
The biggest strength of C++ is components. For example, when in your program
you have a File menu and the file dialog opens, this comes from a file
comdlg32.dll. It's called Common Dialogs. This component is used by almost
all (Windows based) programs that open/close files. When the application is
reworked for 64-bits, it is recompiled with minimum change of the source
files. However 64-bit app will not call comdlg32.dll, but some other 64-bit
..dll file. During the time of VC++ 6.0 , there was a period known as "DLL
Hell". It was because more apps could use the same dll file and one app
could overwrite the newer dll and replace it with the older version. Also,
when uninstalled, an app could have removed a dll that other apps might have
still been using.
Anyway, this situation is now solved and the chances of running into "DLL
Hell" are very slim.

"Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
news:5BD2FB00-9D06-47EA-8F0E-946CA7EF85BF@microsoft.com...
> Dusko, I'm not sure what you mean by "mixing 32-bit and 64-bit
> components".
> Could you please explain. Thank you.
>
> "Dusko Savatovic" wrote:
>
>> Ron, your case is exception to the rule. It seems that your app is hard
>> coded for '\Program Files' instead of %ProgramFiles%. Besides, it was
>> made
>> with Visual C++ 6.0. IIRC Visual C++ 6.0 did not create 64-bit apps. So
>> there's no danger of mixing 32-bit and 64-bit components of that same
>> name
>> ie it's unlikely that another 64-bit app will reference the same
>> component
>> (only it's 64-bit version), but get the 32-bit version instead.
>>
>>
>> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
>> news:B65518F9-E857-4E15-AAC8-32F72F34B2BD@microsoft.com...
>> > 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@discussions.microsoft.com> wrote in
>> >> message
>> >> news:525FAA21-4A40-496A-ADC4-FE7B4D336961@microsoft.com...
>> >> > 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@discussions.microsoft.com> wrote in
>> >> >> message
>> >> >> news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@microsoft.com...
>> >> >> >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@discussions.microsoft.com> wrote
>> >> >> >> in
>> >> >> >> message
>> >> >> >> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
>> >> >> >> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com>
>> >> >> >> >> wrote
>> >> >> >> >> in
>> >> >> >> >> message
>> >> >> >> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
>> >> >> >> >> > 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.
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>>
>>
Re: Microsoft Visual C++ Runtime Library Runtime Error [message #164838 is a reply to message #164322] Thu, 02 July 2009 12:53 Go to previous message
Ron Sochanski  is currently offline Ron Sochanski
Messages: 10
Registered: August 2009
Junior Member
You were right! My app was hard-coded with '\Program Files' instead of
%ProgramFiles%. I did not realize this. I have modified the app to use
%ProgramFiles% instead and my problem has been solved. Thanks very much for
your help and insight.

"Dusko Savatovic" wrote:

> The biggest strength of C++ is components. For example, when in your program
> you have a File menu and the file dialog opens, this comes from a file
> comdlg32.dll. It's called Common Dialogs. This component is used by almost
> all (Windows based) programs that open/close files. When the application is
> reworked for 64-bits, it is recompiled with minimum change of the source
> files. However 64-bit app will not call comdlg32.dll, but some other 64-bit
> ..dll file. During the time of VC++ 6.0 , there was a period known as "DLL
> Hell". It was because more apps could use the same dll file and one app
> could overwrite the newer dll and replace it with the older version. Also,
> when uninstalled, an app could have removed a dll that other apps might have
> still been using.
> Anyway, this situation is now solved and the chances of running into "DLL
> Hell" are very slim.
>
> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
> news:5BD2FB00-9D06-47EA-8F0E-946CA7EF85BF@microsoft.com...
> > Dusko, I'm not sure what you mean by "mixing 32-bit and 64-bit
> > components".
> > Could you please explain. Thank you.
> >
> > "Dusko Savatovic" wrote:
> >
> >> Ron, your case is exception to the rule. It seems that your app is hard
> >> coded for '\Program Files' instead of %ProgramFiles%. Besides, it was
> >> made
> >> with Visual C++ 6.0. IIRC Visual C++ 6.0 did not create 64-bit apps. So
> >> there's no danger of mixing 32-bit and 64-bit components of that same
> >> name
> >> ie it's unlikely that another 64-bit app will reference the same
> >> component
> >> (only it's 64-bit version), but get the 32-bit version instead.
> >>
> >>
> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com> wrote in message
> >> news:B65518F9-E857-4E15-AAC8-32F72F34B2BD@microsoft.com...
> >> > 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@discussions.microsoft.com> wrote in
> >> >> message
> >> >> news:525FAA21-4A40-496A-ADC4-FE7B4D336961@microsoft.com...
> >> >> > 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@discussions.microsoft.com> wrote in
> >> >> >> message
> >> >> >> news:169A3AE7-DFE5-4DF1-9423-36CFAAB3F4BF@microsoft.com...
> >> >> >> >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@discussions.microsoft.com> wrote
> >> >> >> >> in
> >> >> >> >> message
> >> >> >> >> news:8BBF6641-BC97-433B-B91C-9C65E78B6FF2@microsoft.com...
> >> >> >> >> > 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=BD2 A6171-E2D6-4230-B809-9A8D7548C1B6&displaylang=en
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >> >> "Ron Sochanski" <RonSochanski@discussions.microsoft.com>
> >> >> >> >> >> wrote
> >> >> >> >> >> in
> >> >> >> >> >> message
> >> >> >> >> >> news:B662044C-74FF-4B83-A062-276CC5C55920@microsoft.com...
> >> >> >> >> >> > 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.
> >> >> >> >> >>
> >> >> >> >> >>
> >> >> >> >>
> >> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >>
> >>
>
>
Previous Topic:Windows Server 2003 64bit (task Scheduler not working)
Next Topic:don't get how to use groups
Goto Forum:
  


Current Time: Tue Aug 22 03:19:33 EDT 2017

Total time taken to generate the page: 0.10030 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software