/build/static/layout/Breadcrumb_cap_w.png

Setup won´t start.... Problems with WInstaller version??

Hi,

i use windows server 2003 and i´m trying to install sql server 2000 but when i double-click the setup file it does nothing.

i installed windows installer version 3.1 yesterday. Could this be the problem?

Thanks in advance
Sara

0 Comments   [ + ] Show comments

Answers (3)

Posted by: MSIMaker 15 years ago
2nd Degree Black Belt
0
Make sure your user rights allow you to install applcations to the server. By default Windows 2003 server is more strict than 2000 server.
Posted by: topeson 12 years ago
Yellow Belt
0
I have Microsoft(R) Windows(R) Server 2003 for Small Business Server Version 5.2.3790 Service Pack 2 Build 3790. I
have the latest win installer 4.5 installed.
While installing the BitDefender Management Server and Console, I get this error at the tail end of my installation that says "There is a problem with this windows installer package. A program run as part of the setup
did not finish as expected".
Now regularly I have this message "The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2755." This is preventing me from installing this antivirus that I have bought. I believe this forum has a lot for me so I decided to make my post here as I am in a fix!!! Seems to me that my windows installer program is fine as I can install other modules from the same program. However when it comes to the "Management Server and Console" module all this error occur at the tail end of the install process. I don't know anyway. Can someone help?
Posted by: anonymous_9363 12 years ago
Red Belt
0
Run the install again but this time, as ever, with verbose logging. This will point to the exact location in the MSI where the actual error is occuring.

Meanwhile, you're right. This forum (the whole site, actually) has much to offer you. Check out http://itninja.com/question/help-with-msi-1330 which seems to indicate that the set-up executable is trying to write files in a location where the account you are using doesn't have write access. My guess would be a registry key but it's pure guesswork. The log file will help you determine that.

Oh, BTW, please don't resurrect old threads with what is a new issue. Thanks.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ