|
-
Apr 23rd, 2003, 09:33 AM
#1
Thread Starter
Lively Member
Deployment error (the install keeps rolling back)
I have built a setup project to deploy a migration utility that migrates a clients data up to SQL Server. When you run the install, I install the files then launch the app to migrate the data after the app is done it shuts down then the finish screen is suppose to display.
Problem: When the app completes, it shuts down and then the install is suppose to go to the finish screen but it errors out and gives me a generic msg "There is a problem with the install" then rolls back the entire process.
I have built the entire solution in both debug and release mode and that did not make a difference. I have also created a custom action in the install section and the commit section (when to launch the app during the install) and neither one made a difference either. I am unable to trap the error, so I have no clue what is causing it.
Does anyone have any idea what may be causing this error? The migration application runs approximately for about 8 minutes. Would it have anything to do with the legnth of the migration process?
-
Apr 23rd, 2003, 01:10 PM
#2
Frenzied Member
Cant you try it on another machine to see if it still faces error?
'Heading for the automatic overload'
Marillion, Brave, The Great Escape, 1994
'How will WE stand the FIRE TOMORROW?'
Eloy, Silent Cries and Mighty Echoes, The Vision - Burning, 1979
-
Apr 23rd, 2003, 01:15 PM
#3
Thread Starter
Lively Member
yeah, I gave it to a user to test it and it happened to them. Its weird, I ran it twice on my machine last night and it worked fine. When the user ran it the first time she said it worked. She then wanted to try it again, so she uninstalled it then re-installed it and it failed.
-
Apr 23rd, 2003, 01:32 PM
#4
Frenzied Member
Cant you let the users run the program when the installation finishes, just like normal setups, and do not launch the application during setup to isolate the problem?
'Heading for the automatic overload'
Marillion, Brave, The Great Escape, 1994
'How will WE stand the FIRE TOMORROW?'
Eloy, Silent Cries and Mighty Echoes, The Vision - Burning, 1979
-
Apr 23rd, 2003, 02:25 PM
#5
Thread Starter
Lively Member
yeah, I may be forced to do that. I was just trying to automate the entire process.
-
Apr 24th, 2003, 04:39 AM
#6
Registered User
Hi, are u using any transactions while uploading the dat is yes then I think whats happening here is that the transactions are interfering with each other or u can say there is is clash in transactions of ur app and installer, it could also be due to a simple reason like there is some dll giving an error (thats why ur tester was able to install it first time but on second attempt it failed) it will be better if u segregate ur installer and app.
-
Apr 24th, 2003, 07:11 AM
#7
Thread Starter
Lively Member
No transactions are being used. What do you mean segregate the app from the intaller?
-
Apr 24th, 2003, 11:35 PM
#8
Registered User
i meant first let the installation be completed then launch ur app not while setup is running.
-
Apr 25th, 2003, 10:28 AM
#9
Thread Starter
Lively Member
How would I be able to launch the app when the setup is done?
Right now I am launching the app during the install.
If the setup is complete how is that possible?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|