Make sure that you do the following:
- From: Adrian H
- Date: Mon, 09 Nov 2009 14:07:25 -0800
It turns out that you need not only the .dll files, but the .manifest files as well. Once done, it will register correctly.
Enjoy.
Adrian
RK Sharma wrote:
VS2008 DLL not loading
05-Mar-09
Any resolution to this. I am having exactly the same problem and am stumped.
Previous Posts In This Thread:
On Friday, December 28, 2007 4:14 PM
harold wrote:
VS2008 DLL not loading
I am working with unmanaged C++ DLL project, the DLL created is loaded into
an application (that I do not have the source) as an addin to the application.
In VS2005 both the release and debug versions of the DLL loaded fine (at
seperate times of course), but after converting the project to VS2008 only
the release version of the DLL loads, the debug version does not.
No other changes were made except for the conversion from VS2005 to VS2008.
Can someone help me fugure out why the debug version of the DLL will not load?
--
Harolds
On Sunday, December 30, 2007 10:00 PM
jeta wrote:
Hi Harolds,Can you provide more details regarding this issue?
Hi Harolds,
Can you provide more details regarding this issue? What exception do you
get during failure? What is the stack trace of the failure?
Also, how does the application loads your dll, statically linked or using
LoadLibrary? It would be helpful if you can provide a sample project to
reproduce this problem. If so, you may attach it a further reply using
Outlook Express.
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
On Monday, December 31, 2007 12:35 PM
Phil Wilson wrote:
My guess is that the debug version of the CRT for Visual Studio 2008 is
My guess is that the debug version of the CRT for Visual Studio 2008 is
missing. If you run dependencywalker on the Dll on the failing system it
should show you.
--
Phil Wilson
[Microsoft MVP-Windows Installer]
"Harolds" <harolds@xxxxxxxxxxxxx> wrote in message
news:8E1F02FA-D0EE-42D3-AE20-EB86BA8F01EB@xxxxxxxxxxxxxxxx
On Monday, December 31, 2007 4:11 PM
harold wrote:
Re: VS2008 DLL not loading
dependencywalker shows the following:
Release Version:
MFC90.DLL could not find MSVCR90.DLL - though my.DLL shows it loaded
MSVCR90.DLL
MSVCP90.DLL could not find MSVCR90.DLL - though my.DLL show it loaded
MSVCR90.DLL
Debug Verion:
MFC90D.DLL could not find MSVCR90D.DLL - though my.DLL shows it loaded
MSVCR90D.DLL
MSVCP90D.DLL could not find MSVCR90D.DLL - though my.DLL show it loaded
MSVCR90D.DLL
my.DLL could not find MSVCR90.DLL
Why would it be trying to load a nondebug DLL?
--
Harolds
"Phil Wilson" wrote:
On Monday, December 31, 2007 4:21 PM
harold wrote:
Please see my response to Phil Wilson's suggestion.
Please see my response to Phil Wilson's suggestion.
Thank you,
--
Harolds
""Jeffrey Tan[MSFT]"" wrote:
On Tuesday, January 01, 2008 9:49 PM
jeta wrote:
Hi Harolds,Thanks for your feedback.
Hi Harolds,
Thanks for your feedback.
Do you mean that your dll statically linked with the MSVCR90.DLL but loader
and dependency walker can not find it? Since your dll statically linked
with the MSVCR90.DLL, have you tried to find out which function does your
dll import from MSVCR90.DLL? You may just use "dumpbin /imports" to examine
your dll imports API list and find the category for MSVCR90.DLL.
For testing purpose, I created a normal win32 GUI project in VS2008, but I
did not find any modules linked with MSVCR90.DLL yet.
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
On Thursday, January 03, 2008 11:44 AM
harold wrote:
Re: VS2008 DLL not loading
When I run C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\dumpbin.exe I
get "The application failed to start because mspdb80.dll was not found".
--
Harolds
""Jeffrey Tan[MSFT]"" wrote:
On Friday, January 04, 2008 3:57 AM
jeta wrote:
Hi Harolds,Thanks for the feedback.You should run dumpbin.
Hi Harolds,
Thanks for the feedback.
You should run dumpbin.exe from the VS2005 or VS2008 command
prompt(Microsoft Visual Studio 2005->Visual Studio Tools->Visual Studio
2005 Command Prompt) instead of normal cmd.exe. The VS2005 command prompt
contains more environment variable paths than normal cmd.exe. For example,
mspdb80.dll resides in "D:\Microsoft Visual Studio 8\Common7\IDE\". VS2005
command prompt can find it but cmd.exe can not find it.
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
On Friday, January 04, 2008 4:13 PM
harold wrote:
I don't know what I was thinking, I knew I needed to run it using VS2008
I don't know what I was thinking, I knew I needed to run it using VS2008
command prompt.
Here what is says about MSVCR90.DLL:
MSVCR90.dll
10188C68 Import Address Table
101883C4 Import Name Table
0 time date stamp
0 Index of first forwarder reference
58A wcscpy
40E _vsnprintf_s
412 _vsnwprintf_s
375 _snwprintf_s
58B wcscpy_s
593 wcsncpy_s
4C4 calloc
337 _recalloc
431 _wcsicmp
58E wcslen
36D _snprintf_s
18A _fileno
--
Harolds
""Jeffrey Tan[MSFT]"" wrote:
On Sunday, January 06, 2008 10:37 PM
jeta wrote:
Hi Harolds,Thanks for your feedback.Is your my.dll that linked with MSVCR90.
Hi Harolds,
Thanks for your feedback.
Is your my.dll that linked with MSVCR90.dll? It looks strange that your dll
will link with the release version of VC runtime. I have tried to search
this type of issue in internal database; I only find one issue talking
about that debug version using ATL library will link with release VC
runtime because ATL is built with release build.
I suspect there may be some configuration problem in your project or IDE.
Can you enable verbose output in the linker option and paste the output in
"Output" window here? I am not sure if this will enlighten the root cause,
but it should worth to examine:
1. Open the project's Property Pages dialog box.
2. Click the Linker folder.
3. Click the Command Line property page.
4. Type the "/VERBOSE" into the Additional Options box.
Additionally, is this problem only occur with your updating project? If you
create an empty one with similar code, do you get the same problem? Have
you tried to move your project to a new VS2008 machine for reproduce?
Anyway, I will contact VC++ team for some more advice. Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
On Monday, January 07, 2008 12:42 PM
harold wrote:
"Is your my.dll that linked with MSVCR90.dll?
"Is your my.dll that linked with MSVCR90.dll?": No, like I said VS2005 works
fine.
"If you create an empty one with similar code, do you get the same
problem?": Large project, so I haven't tried this.
"Have you tried to move your project to a new VS2008 machine for
reproduce?": Same problem.
When including the verbose I got the following:
Your post is too long. Please reduce the amount of text. (Limit = 30000,
Current = 160128)
On Tuesday, January 08, 2008 1:56 AM
jeta wrote:
Hi Harolds,Thanks for your feedback.
Hi Harolds,
Thanks for your feedback.
I have discussed the VC++ team over this issue. Can you make sure that the
debug version of the CRT (msvcr90d.dll) is installed in the WinSxs
(c:\windows\winsxs)? And can you check that the application or the dll got
the proper manifest to load msvcr90d.dll? We believe once the dll has the
correct manifest and your system has msvcr90d.dll installed the fusion
loader can find the msvcr90d.dll without any problem.
If you are running on Vista, using sxstrace is a great way to get extra
information for debugging SxS load failures. Instructions on using sxstrace
are below, about 2/3rds of the way down the page:
"Diagnosing SideBySide failures"
http://blogs.msdn.com/junfeng/archive/2006/04/14/576314.aspx
If you are not running Vista, you may try to use Process Monitor to log the
file system activities of your application startup. If you have pay special
attention to VC runtime dll probings such as msvcr90d.dll, MSVCR90.dll. You
may download Process Monitor in the link below:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
On Tuesday, January 08, 2008 12:13 PM
harold wrote:
Re: VS2008 DLL not loading
msvcr90d.dll is located in:
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2
I opened a command prompt with run as administrator and completed the steps:
sxstrace trace -logfile:sxstrace.etl
start the app that uses the debug dll
sxstrace parse -logfile:sxstrace.etl -outfile:sxstrace.txt
And the sxstrace.txt was empty.
--
Harolds
""Jeffrey Tan[MSFT]"" wrote:
On Wednesday, January 09, 2008 3:56 AM
jeta wrote:
Hi Harolds,This looks strange, because I can follow the exact steps and get a
Hi Harolds,
This looks strange, because I can follow the exact steps and get a detailed
log file. Do you see the successful messages outputed by sxstrace.exe. The
text I got from elevated cmd.exe from my Vista machine:
C:\Windows\system32>sxstrace trace -logfile:sxstrace.etl
Tracing started. Trace will be saved to file sxstrace.etl.
Press Enter to stop tracing...
C:\Windows\system32>sxstrace parse -logfile:sxstrace.etl
-outfile:sxstrace.txt
Parsing log file sxstrace.etl...
Parsing finished! Output saved to file sxstrace.txt.
You may also try to run this Exe from VS2008 command prompt although I can
get both normal cmd.exe and VS2008 command prompt to work.
If this still does not work, have you tried to use Process Monitor to get
some informative records?
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
On Wednesday, January 09, 2008 6:18 PM
harold wrote:
I see the exact same messages that you have.I cannot find procmon.
I see the exact same messages that you have.
I cannot find procmon.exe anywhere on my computer.
--
Harolds
""Jeffrey Tan[MSFT]"" wrote:
On Thursday, January 10, 2008 9:21 PM
jeta wrote:
Hi Harolds,Sorry for the late response, I am out of office yesterday.
Hi Harolds,
Sorry for the late response, I am out of office yesterday.
Have you tried to run your problematic application after enabling "sxstrace
trace"? Note: you should not press "Enter" key to stop the tracing before
running your problematic application.
For Process Monitor, I think I have provided you the download in the
previous reply:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
You may enter your application name in the filter for "Process Name"
column, so that Process Monitor will only show your application process
activity records. Also, you may press the button in the toolbar to hide the
registry activities. Also, you may pay special attention to records contain
"msvcr" substring. They indicate the VC++ runtime file system probings.
Please feedback any progress here, thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
On Monday, January 14, 2008 6:13 PM
harold wrote:
You can see below where mydll.Dll is loaded then pthreadVC2.
You can see below where mydll.Dll is loaded then pthreadVC2.dll is loaded,
you also see where msvcr90d.dll is loaded, but after msvcp90d.dll is loaded
msvcr90.dll cannot be found:
C:\App_Dir\Plugins\Mydll.dll SUCCESS
C:\App_Dir\Plugins\Mydll.dll SUCCESS
C:\App_Dir\pthreadVC2.dll FAST IO DISALLOWED
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\pthreadVC2.dll SUCCESS
C:\App_Dir\App.exe.Local FAST IO DISALLOWED
C:\App_Dir\App.exe.Local NAME NOT FOUND
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8 FAST IO DISALLOWED
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8\msvcr80.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8\msvcr80.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8\msvcr80.dll SUCCESS
C:\App_Dir\App.exe.Local FAST IO DISALLOWED
C:\App_Dir\App.exe.Local NAME NOT FOUND
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5 FAST IO DISALLOWED
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5\mfc90d.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5\mfc90d.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5\mfc90d.dll SUCCESS
C:\App_Dir\App.exe.Local FAST IO DISALLOWED
C:\App_Dir\App.exe.Local NAME NOT FOUND
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2 FAST IO DISALLOWED
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2\msvcr90d.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2\msvcr90d.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2\msvcr90d.dll SUCCESS
C:\App_Dir\MSIMG32.dll FAST IO DISALLOWED
C:\App_Dir\MSIMG32.dll NAME NOT FOUND
C:\Windows\System32\msimg32.dll FAST IO DISALLOWED
C:\Windows\System32\msimg32.dll SUCCESS
C:\Windows\System32\msimg32.dll SUCCESS
C:\Windows\System32\msimg32.dll SUCCESS
C:\Windows\System32\msimg32.dll SUCCESS
C:\Windows\System32\msimg32.dll SUCCESS
C:\Windows\System32\msimg32.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2\msvcp90d.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2\msvcp90d.dll SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2\msvcp90d.dll SUCCESS
C:\App_Dir\MSVCR90.dll FAST IO DISALLOWED
C:\App_Dir\MSVCR90.dll NAME NOT FOUND
C:\Windows\System32\MSVCR90.dll FAST IO DISALLOWED
C:\Windows\System32\MSVCR90.dll NAME NOT FOUND
C:\Windows\system\MSVCR90.dll FAST IO DISALLOWED
C:\Windows\system\MSVCR90.dll NAME NOT FOUND
C:\Windows\MSVCR90.dll FAST IO DISALLOWED
C:\Windows\MSVCR90.dll NAME NOT FOUND
C:\App_Dir\MSVCR90.dll FAST IO DISALLOWED
C:\App_Dir\MSVCR90.dll NAME NOT FOUND
C:\Windows\System32\MSVCR90.dll FAST IO DISALLOWED
C:\Windows\System32\MSVCR90.dll NAME NOT FOUND
C:\Windows\MSVCR90.dll FAST IO DISALLOWED
C:\Windows\MSVCR90.dll NAME NOT FOUND
C:\Windows\System32\wbem\MSVCR90.dll FAST IO DISALLOWED
C:\Windows\System32\wbem\MSVCR90.dll NAME NOT FOUND
C:\Program Files\ATI Technologies\ATI.ACE\Core-Static\MSVCR90.dll FAST IO
DISALLOWED
C:\Program Files\ATI Technologies\ATI.ACE\Core-Static\MSVCR90.dll NAME NOT
FOUND
C:\Windows\System32\WindowsPowerShell\v1.0\MSVCR90.dll FAST IO DISALLOWED
C:\Windows\System32\WindowsPowerShell\v1.0\MSVCR90.dll NAME NOT FOUND
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\MSVCR90.dll FAST IO
DISALLOWED
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\MSVCR90.dll NAME NOT FOUND
C:\Windows\winsxs\x86_microsoft.vc90.debugcrt_1fc8b3b9a1e18e3b_9.0.21022.8_none_96748342450f6aa2 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc90.debugmfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_9b54853441e399d5 SUCCESS
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8 SUCCESS
--
Harolds
""Jeffrey Tan[MSFT]"" wrote:
On Wednesday, January 16, 2008 4:50 AM
jeta wrote:
Hi Harolds,From this log file, we can only find out that the fusion loader is
Hi Harolds,
From this log file, we can only find out that the fusion loader is notprobing Winsxs folder for MSVCR90.dll.
Looking at the nature of this issue and due to the support limitation of
newsgroup, it would require intensive troubleshooting which would be done
quickly and effectively with direct assistance from a Microsoft Support
Professional through Microsoft Product Support Services.
You can contact Microsoft Product Support directly to discuss additional
support options you may have available, by contacting us at 1-(800)936-5800
or by choosing one of the options listed at:
http://www.microsoft.com/services/microsoftservices/srv_support.mspx
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
On Thursday, March 05, 2009 1:13 PM
RK Sharma wrote:
VS2008 DLL not loading
Any resolution to this. I am having exactly the same problem and am stumped.
On Monday, November 09, 2009 5:05 PM
Adrian H wrote:
Make sure that you do the following:
It turns out that you need not only the .dll files, but the .manifest files as well. Once done, it will register correctly.
Enjoy.
Adrian
On Monday, November 09, 2009 5:07 PM
Adrian H wrote:
Make sure that you do the following:
It turns out that you need not only the .dll files, but the .manifest files as well. Once done, it will register correctly.
Enjoy.
Adrian
EggHeadCafe - Software Developer Portal of Choice
Silverlight 2 Beta 2 - Doing Data Part I
http://www.eggheadcafe.com/tutorials/aspnet/5091fa75-2e9b-40d4-88cc-58558a7e83f8/silverlight-2-beta-2--do.aspx
.
- Prev by Date: Make sure that you do the following:
- Next by Date: Make sure that you do the following:
- Previous by thread: Make sure that you do the following:
- Next by thread: Make sure that you do the following:
- Index(es):
Relevant Pages
|
