Install built with latest version of installaware Studio. Applcation is .NET Windows forms application built with Visual Studio 2010.
Installation is working fine on workstations and I tried on Server 2008 R2 box I have here, two separate customers are getting this error on their Windows Server 2008 Standard boxes when the installation process begins (after choosing the destination location and pogram group dialog) where it would begin installing the files. It did not recognize that it was missing any of the prerequisites and it should not be.
Running as Administrator. Tried EXE and MSI version of the install. Tried putting the server in install mode via "change user /install"
Stopped working
Windows can check online for a solution to the problem.
Problem Details
Problem signature:
Problem Event Name: BEX
Application Name: WisdomAccountingSuite.exe
Application Version: 14.3.0.5
Application Timestamp: 512e396c
Fault Module Name: StackHash_4ccf
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 03acfdc6
Exception Code: c0000005
Exception Data: badc0de1
OS Version: 6.0.6002.2.2.0.16.7
Locale ID: 1033
Additional Information 1: 4ccf
Additional Information 2: bef63156bfe57062661cf2233ec8a61f
Additional Information 3: ff24
Additional Information 4: a59eca1300cc63414fbbe2a265913bac
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409
Installation crashing on Server 2008 Standard
-
- Posts: 18
- Joined: Wed Oct 17, 2007 4:44 pm
- Location: Arizona, USA
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Installation crashing on Server 2008 Standard
Dear User,
It is not easy to find out what happens without having your project.
First of all, I may suggest you to place some MessageBoxes in your code, in order to identify where in your script the error is generated.
You can also try if a logged setup execution reports any useful information.
To run a logged execution of a compressed exe, use;
- <setup.exe> /l=<path to logfile>
to generate a verbose log of a MSI package, use:
- msiexec /i <MsiPackage Name> /L*V <path to logfile>
Regards
It is not easy to find out what happens without having your project.
First of all, I may suggest you to place some MessageBoxes in your code, in order to identify where in your script the error is generated.
You can also try if a logged setup execution reports any useful information.
To run a logged execution of a compressed exe, use;
- <setup.exe> /l=<path to logfile>
to generate a verbose log of a MSI package, use:
- msiexec /i <MsiPackage Name> /L*V <path to logfile>
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
-
- Posts: 18
- Joined: Wed Oct 17, 2007 4:44 pm
- Location: Arizona, USA
Re: Installation crashing on Server 2008 Standard
Thanks for the reply. I will have the user try the install and create a log. Sorry, I forgot about that option. I am using the MSICode Call DLL function with kernel32.dll right about where the application is dying. Based on some other issues I read about with Server 2008 Standard on this forum, I am removing these lines. The purpose was to show differnet flash at different points in the installation. If there's a better way to do this, I'd be interested in hearing it.
~InstallAware Clipboard Data~
~Call DLL Function~
~{BFD3B59C-7835-4A85-9F9B-B0786C7FFD37}~
~$WINSYSDIR$\\kernel32.dll,CopyFile,bool,LASTERROR,"pointer to string",$SUPPORTDIR$\\movie2.swf,"pointer to string",$SUPPORTDIR$\\movie.swf,$~
~mIDEFunc.dll\mEXEFunc.dll~
~Call DLL Function~
~{802FCD2B-E112-422F-9A53-EFC361407713}~
~$WINSYSDIR$\\kernel32.dll,DeleteFileA,bool,LASTERROR,"pointer to string",$SUPPORTDIR$\\movie.swf,$~
~mIDEFunc.dll\mEXEFunc.dll~
~Call DLL Function~
~{256416E3-854E-439A-86A8-51CEBFA69858}~
~$WINSYSDIR$\\kernel32.dll,CopyFile,bool,LASTERROR,"pointer to string",$SUPPORTDIR$\\movie.swf,"pointer to string",$SUPPORTDIR$\\movie1.swf,$~
~mIDEFunc.dll\mEXEFunc.dll~
Comment: Call DLL Function $WINSYSDIR$\\kernel32.dll->CopyFile (get result into variable LASTERROR)
Comment: Call DLL Function $WINSYSDIR$\\kernel32.dll->DeleteFileA (get result into variable LASTERROR)
Comment: Call DLL Function $WINSYSDIR$\\kernel32.dll->CopyFile (get result into variable LASTERROR)
I'll post the results of this new version of the install and if it fails a log from the install.
Quinton
~InstallAware Clipboard Data~
~Call DLL Function~
~{BFD3B59C-7835-4A85-9F9B-B0786C7FFD37}~
~$WINSYSDIR$\\kernel32.dll,CopyFile,bool,LASTERROR,"pointer to string",$SUPPORTDIR$\\movie2.swf,"pointer to string",$SUPPORTDIR$\\movie.swf,$~
~mIDEFunc.dll\mEXEFunc.dll~
~Call DLL Function~
~{802FCD2B-E112-422F-9A53-EFC361407713}~
~$WINSYSDIR$\\kernel32.dll,DeleteFileA,bool,LASTERROR,"pointer to string",$SUPPORTDIR$\\movie.swf,$~
~mIDEFunc.dll\mEXEFunc.dll~
~Call DLL Function~
~{256416E3-854E-439A-86A8-51CEBFA69858}~
~$WINSYSDIR$\\kernel32.dll,CopyFile,bool,LASTERROR,"pointer to string",$SUPPORTDIR$\\movie.swf,"pointer to string",$SUPPORTDIR$\\movie1.swf,$~
~mIDEFunc.dll\mEXEFunc.dll~
Comment: Call DLL Function $WINSYSDIR$\\kernel32.dll->CopyFile (get result into variable LASTERROR)
Comment: Call DLL Function $WINSYSDIR$\\kernel32.dll->DeleteFileA (get result into variable LASTERROR)
Comment: Call DLL Function $WINSYSDIR$\\kernel32.dll->CopyFile (get result into variable LASTERROR)
I'll post the results of this new version of the install and if it fails a log from the install.
Quinton
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Installation crashing on Server 2008 Standard
Dear Quinton,
maybe I'm wrong ... but I suspect the error could be caused by the "CopyFile" function call.
You should explicitly use the "CopyFileA" WINAPI declaration with the "Call DLL Function" command name parameter... and not "CopyFile".
Regards.
maybe I'm wrong ... but I suspect the error could be caused by the "CopyFile" function call.
You should explicitly use the "CopyFileA" WINAPI declaration with the "Call DLL Function" command name parameter... and not "CopyFile".
Regards.
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Who is online
Users browsing this forum: No registered users and 153 guests