469,963 Members | 1,885 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,963 developers. It's quick & easy.

Setup problem VB.net 2005

Hi All

I have an application with a setup project which has worked faultlessly for

Today I added some graphs to the Report viewer in VB.net 2005 and when I
build the setup project and try to install on a PC I get the error message

Exception occurred while initialising the installation
Syystem.IO.FileNotFoundException. Could not load file or assembly
file:///C:\Windows\system32\setup\CD\ or one of its dependencies.
The system cannot find the file specified

How can I debug the setup project to find which file is missing?
Oct 13 '06 #1
1 1485
Hi Steve,

Based on the description, you add some graphs to the Report viewer in your
VB.NET 2005 application, then create a VS2005 setup project for that
application. The problem occurs while initializing the installation process
to install the VB.NET 2005 application on a client machine. Please correct
me if I misunderstood anything.

According to the error message:

"Could not load file or assembly file:///C:\Windows\system32\setup\CD\ or
one of its dependencies."

It seems not one of your application's dependencies absent, but one Windows
system dependency files cannot be loaded in the target machine's
Windows\system32\setup\CD\ directory. This could be caused by one of the
Windows components(which is necessary to the installation process) hasn't
been installed on the target client machine.

Since the error message doesn't tell us which dll it tries to load, I
suggest you launch that installation package with a log option. You can
perform this as the following in the the target client machine's command

msiexec /iVBApp.msi /l*v log.txt

The detailed log information would be logged into the log.txt file, you can
check it for which exact dll missing in the installation.


Best regards,

Gary Chang
Microsoft Online Community Support
Get notification to my posts through email? Please refer to

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
This posting is provided "AS IS" with no warranties, and confers no rights.

Oct 16 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by StevenBarnes | last post: by
reply views Thread by dotnetprogrammer via DotNetMonster.com | last post: by
1 post views Thread by Bry | last post: by
3 posts views Thread by WT | last post: by
6 posts views Thread by andrewbb | last post: by
2 posts views Thread by Norman Diamond | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.