Problem Installing VB2003/.Net 1.1 program on Vista/Win 7

Question

0.00/5 (No votes)

See more:

I have a large VB 2003/.Net 1.1 program that installs on XP with no problems. A 2009 version will install on Vista and Win 7 without a problem. Versions generated in 2010 and 2011, which do not include any new VS/VB controls (that is not used in earlier versions) or other not previously used .Net 1.1 features, just bug fixes and more program functions, still install on XP. But, it has problems installing on Vista and Win7. The .msi file is produced using the VS 2003 "packager".

The install runs to completion then gives a security warning and rolls back: depending on what we try the message may vary but the overall process is the same, run to completion then an error, usually about not having sufficient privileges or other security related message. We have tried using XP mode but without success. The only account on both the Vista and Win 7 machines is the one Admin. account.

Anyone have any idea what MS did to .Net 1.1 or VB 2003 in 2010 that causes this problem? Workarounds or solutions????

Additional info: (1)The program is not "signed", could that be the problem? But neither is the 2009 version (2) the program uses a C++ 6.0 OCX program. But since the same program is in the 2009 version, without any changes, I don't think it is the problem

Any and all suggestions are welcome at this time-- I'm very frustrated after a year of trying...

Posted 16-Dec-11 14:36pm

Charles Wolfe

Updated 16-Dec-11 15:22pm

v4

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2011-12-16T14:53:00

Solution 1

Without knowing the exact error message, everyong is just guessing.

You can get the installation log to see what the MSI was trying to do at the time of the failure. Launch your installation using this (assuming it's an MSI):

msiexec /i <path to="" .msi=""> /l* <path to="" log="" file=""></path></path>

You'll get quite a lot of information in the log file. Just search for "ERROR" and you can start tracing backwards from there seeing what the MSI was doing.

Posted 16-Dec-11 14:53pm

Dave Kreskowiak

Comments

Charles Wolfe 17-Dec-11 20:21pm

I was going to include the error info, but lost/misplaced the msiexec output. Guess I'll have to rerun it next time I have access to one of the "misbehaving" machines and update my question. As I recall it was not really clear about what the EXACT problem is, or I'd have had a clue as to how to proceed.