Has anyone packaged Thomson Reuters FBTSimplifier 2011 classic edition for win 7?
I have captured the app and created msi.Actually it has sql 2005 express edition as pre-req.
The problem is when I install my msi and launch the main shortcut it starts repairing.
Then it gives error saying "servername\sqlexpress not found.check wid ur IT department".
has anyone got this problem before?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
How you installed the prerequisite?

Have you checked event viewer? I beleive that there is some hard coded path in your intsallation.
Answered 05/31/2011 by: naveen.packager
Green Belt

Please log in to comment
0
I installed the pre-req properly.
But while installing main app " machinename\sqlexpress " was populated in one of the fields.
Can it be because of it ? If it is so then how to resolve it?
Answered 05/31/2011 by: yogesh101
Senior Yellow Belt

Please log in to comment
0
Is it self healing in admin mode itself?

First check the Event Viewer and find out which component is getting self healed.

But while installing main app " machinename\sqlexpress " was populated in one of the fields.
Can it be because of it ?


You mean to say that while capturing your application by running setup.exe you got that user input window?

And is the application working in the machine where you have captured it?
Answered 05/31/2011 by: naveen.packager
Green Belt

Please log in to comment
0
yes it is selfhealing in admin itself.
and during capturing it was not my user input but it was automatically
populating with that machinename\sqlexpress.
And now if I install the msi on that capturing machine itself even then it is not working.
Answered 05/31/2011 by: yogesh101
Senior Yellow Belt

Please log in to comment
0
Use PROCMAN while launching the shortcut, you may get some clue.

Try executing the main exe without launching the shortcut.

Check whether SQL Server is running (you might have done it but reminding you if you have not).

Check if it is using any ini file to launch the application and compare it with the source ini file.


For self healing part check the event viewer.

If it works in the machine where it has been captured then you remove that machine name form your capture and add a property or use vbscript to change it as per the installation, if not it will be machine specific.
Answered 05/31/2011 by: naveen.packager
Green Belt

Please log in to comment
0
Can it be because of it ? If it is so then how to resolve it? Your capture probably included the machine name as part of the SQL Server instance name. In the MSI you created from the capture, you need to find that machine name and change it so that it uses the %COMPUTERNAME% environment variable. I would use a Public property for that (so that it could be installed from the command line). Remember that you can't populate that property in the Property table, you'll need to use a Type 51 Custom Action.
Answered 05/31/2011 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity