Steps to produce IDE Crash:
1) Run InnoScript (IS).
2) Receive IS Results per attached.
3) Attempt launch of VB6 IDE:
Receive ~'Can't Load, DAO350.dll not found;
I copy DAO350.dll into folder of VB6.exe;
VB6 then launches but my project can not load.... Receive ~'Can't find messages for other files per red underlined in attached...
InnoScript should Not modify my project or IDE... at least not without asking.
Thank you in advance.
InnoScript does not modify ANYTHING... InnoScript only creates a script. Any modification that would happen would be from the user or the VB6 IDE itself.
We use InnoScript to create InnoScript and there NEVER has been anytime that InnoScript has changed the project file.
You are mis-reading the error file. The error file NEVER states that it is changing anything in your project. It changes information in the InnoScript project and script, NEVER the VB Project file. The error file is for reference ONLY and to be used when you are confused about why a folder or location was changed and where the change came from.
InnoScript does not under ANY circumstances change, move, copy, rename or do ANY type of user file modification at ANY TIME Except when creating a WinSxS installation.
To prove this make a copy of your VBP project file and a copy of your vbp project exe into another location. Run InnoScript on that vbp file then compare that vbp file to your old vbp file. You will find that it is exactly the same, so the modification has to come from somewhere else.
I followed your instructions... result is no change. You are correct that no noticeable change is noticed in the VBP, so must be Other dependency issues?... IDE loads fine until I run IS, then problems per previously discussed.
How can we say that IS is not a factor IF ALL is A-OK (always) until we run IS ?
ie, NO PROBLEMS ...EVER... UNTIL IS IS EXECUTED.
As a futher analysis question, Why does IS show Progam FilesCommon FilesMicrosoft SharedDAODao350.dll - File Does Not Exist but in fact the file IS There (same for all files listed)?
Thank you in advance for your continued support.
I do not believe InnoScript (IS is Inno Setup) reports that it is not there. InnoScript reports in the error log that the path that VB6 uses is not a valid Windows path, Hence the 'Invalid Reference' notation not 'File Not Found'. If in your script you mean that it is in red then InnoScript cannot find it in the path that InnoScript converted the Invalid path to. I do see in the error log that some files are not found and this is because InnoScript cannot locate them in the path that is is using.
The only way that the file would not be found (sort of) is if it were unregistered and not re-registered. This is possible with InnoScript but the file would still be in the same location and not moved, deleted, renamed or modified.
Is it possible to zip and post your project vbp file and the project exe and I will test the results here.
Hi, thx for the quick reply!
As far as my IS designator... MY definition is IS = InnoScript and not anything else.
As far as sending you my VB Project, I can not do that because of proprietary issues....but thank you for the offer!
It appears, from your reply, that Maybe you did not see my original Upload Attachment: IS-IDEcrash1.pdf ?
This attachment is ONLY output from InnoScript per the Log tab.
I think I can send you the complete LOG listing if that might help... I await your reply.
Thank you for your continued support!
There is nothing proprietary in this text file (.vbp file) It is only one text file, not the whole project. And yes I did look at your PDF file, that is what I based my answers upon.
I mis-understood your request... I thought you wanted the full project. I'm uploading the subject VBP now. thx.
It MUST be zipped before posting. Please include the project exe also...
OK, I have verified that InnoScript does not unregister the file in your case. InnoScript will only attempt to get information from the file by unregistering it then re-registering it in a last ditch effort if all other methods fail.
What you can do is go to View->Registered Components on the main menu then search the list to find out where your file is registered before running InnoScript and then after to see if there is any change or if the file is in the list to begin with.
Let's start there...
I'll follow your directions.... tomorrow AM, thx!
Per your directions, the file (my app) is not listed to begin with.
fwiw, I have .MSI install version (from MS VSI) which does work correctly.... It is produced on the same development machine.
Which file are you referring to?
You want to find the DAO350.dll file in the View Registered Components list.
Please define 'works correctly'...
BTW: I have had no problem creating a script from the files you have sent me aside from the files that I don't have that are labeled missing. Other than that everything works as it should. It gets the DAO350.dll file from the Program Files(x86)... folder instead of the Program Files... folder just as it should have because of the reference conversion.
Problem persists; Below steps are results per your directions and your most recent questions for clarification:
1) VB6 IDE launches correctly.
2) InnoScript, View, Registered Components.
3) DAO350.dll listed as registered (ref attached #3 @ Image3Image4.zip).
4) [Create Scrip] selected from InnoScript.
5) InnoScript, View, Registered Components.
6) DAO350.dll listed as registered (ref attached #4 @ Image3Image4.zip).
7) Attempt launch of VB6 IDE: ~Microsoft Visual Basic can't find file 'DAO350.dll'.
8) Check for folder: C:\Program Files\Common Files\Microsoft Shared\DAO\Dao350.dll; Still exists.
Thank you in advance for your support.
fwiw,
step#:
9)Image5 per Image5Image6.zip executed.
10) VB6 launches with error per Image6 per Image5Image6.zip.
fwiw,
step#:
11) Attempted launch of previous working app.exe
12) Non successful: Image7 per Image7.zip is result.
I think I may see the problem from one of your images (Image6.gif). You never mentioned you were attempting to make a WinSxS installation. You should start off with a regular installation until you are versed in InnoScript Operations before attempting to create a WinSxS installation which takes a lot more thought and advanced planning.
I'll assure you that part of the problem is that InnoScript is changing my IDE frame without my authorization.
WinSxS or Not.... All was well before running InnoScript.
I'm presently unable to access my IDE for the app. InnoScript has changed the IDE/App in some way? so that now It Does Not Load.
I currently have an emergency issue where I need to adjust the source code... but It will not load.
Part of the issue is the description. InnoScript is NOT changing your IDE, so continuing in that direction will not result in a solution. Please set InnoScript to NOT create a WinSxS installation then see if you have no problems. I think you will not.
Look at the message carefully. It states that a file is not found in the TEMP folder. The files that are not found just re-register them in their correct location and that problem will be solved. The other is the WinSxS creation without understanding the process. The WinSxS creation will copy files so you would need to be aware of the process.
Issue still persists:
1) I removed all winSxS @ [Add Files].
2) [Create Script] executed.
3) Closed IS after script completed.
4) Attempted launch of my app in IDE; Failure.
Same as previous screen shots.
You did not follow all the steps.
1 - Re-Register all files your project states are missing or you get errors on in their proper locatons.
2 - Open your project to make sure all is working.
3 - Remove WinSxS installation and set to Regular Release
4 - Recreate Script with InnoScript in regular release mode.
In order to create a WinSxS installation, you MUST have a fully working installation to begin with or other issues will come into play as you have noticed.
Also there was a Manifest folder created in the Scripts folder where your project is located. If you could post the WinSxSLog.txt file (WinSxS log file, It starts with your project name exe). I want to see what happened.
I will have a procedure for you to use to correct the issues you have been having with loading your project. When I am done I will post it.
Here is the procedure to get back to the original point.
1 - Open InnoScript
2 - Open a Command Prompt
(Start->Run Type in CMD or in Vista/Window 7 Start->Search Type in CMD.exe when it appears right click and select 'Run As Administrator)
3 - In Innoscript goto View->Registered Components
4 - Click on the location title bar to sort the locations.
5 - Search for one of the files that is getting the error when you open your project.
6 - This line should be in red with all the other missing files next to it.
7 - In Windows go to Start-Run then type in one of the missing files from the list.
8 - In the search list locate where the file should be (IE WindowsSystem32).
9 - Go to the CMD prompt window then change to that folder.
10 - Register the file (IE regsvr32 Filename).
11 - Repeat steps 7 thru 10 until all files are registered.
12 - Open your project.
This will get you back to where you need to be. I will be releasing an update to the WinSxS process to correct this issue. I apologize for the inconvenience. If you need more assistance with this please let me know.
I can not provide you with your requested log file as I was under a time constraint and thus had to restore a previous back-up image for the subject system.
All is well now but I'm at a system config that is Previous to the intro of InnoScript.
I must now, temporarily, abandon the InnoScript project.
Thank you for your support.
Ok, no need for the log I found what the issue was and the fix is in the works. Will release the update when done.
The new version has been release which takes care of the issue you found. You can download it from https://randemsystems.com/innoscript// (https://randemsystems.com/innoscript//)
Thank you for reporting this issue.
Thank you for your support!
Your download appears on my system to be broken:
The unzip to InnoScript1005004Release.exe (11961KB) says it ...Fails CRC Check.
I downloaded twice with same result.
This is Not an immediate issue for me as I'm not Presently working on InnoScript.
Thanks again for your support!
Ok, re-uploading the installations.
Thanks
fwiw:
Upon initial launch, Before app appears, I received Run time error '429': ActiveX Component can't create object.
Then nothing.
Ok, re-uploaded. Download again it should solve the issue.
SxS problems continue:
I apparently have your most recent update, per app checking at launch {ver 10.5 build 4}, and I'm receiving there is a problem with the application on launch attempt after deployment to 3rd party computers when employing InnoScript SxS for the InnoScript recommended files.
All appears ok when not using SxS.
Additionally, when using SxS, InnoScript reregister DAO350.dll and others so that VB6 IDE does not launch, etc.
Yes, you probably will have that error on some applications. It is noted in the manual you will need to figure out which ocx.dll/exe that you are adding to the WinSxS deployment cannot be there then you can add them to the [WinSxS] section of the UnSafe.Fil file. There are some files that will not work in a Side-by-Side environment. You will need to add one file at a time to the WinSxS deployment till you find the file(s) that cannot work in that environment and not add them. It is a trial and error approach but that is the only one that will work consistently.
When using WinSxs if you have files that are to be registered they will be registered as normal. If you have files the are to be deployed as WinSxS, a Manifest will be created for these files and they are NOT registered in the normal fashion.
Please post your script so that I may take a look.
Sorry, I forgot to ask for the manifest file also... Could you zip and post that too.
Have you tried the trial and error approach yet?
In your script you are duplicating lines such as Source: C:\TT-VB6\TrilDistrib_INNO\Manifest\TT-.exe.manifest; DestDir: {app}; Flags: ignoreversion;
You may not be using the templates as you should (recommended) or modifying lines manually (not recommended). When you modify lines manually without using the templates to do the modification; you may forget or not type the lines the same each time leading to incorrect results and/or duplications.
I don't see a database in your script but you have database modules in the script. If you are deploying a database in the {app} folder and it is deployed in the {pf}, {pf32}, {pf64} folders (not recommended) you will experience issues related to maintenance with the database.
InnoScript is designed to help keep you from manually modifying lines so that each time you can generate the same exact script if you need to or modify just the lines you need to automatically.
Please refer to ** insert replies below:
In your script you are duplicating lines such as Source: C:TT-VB6TrilDistrib_INNOManifestTT-.exe.manifest; DestDir: {app}; Flags: ignoreversion;
**
Nope.. no intention to do that... One would think that a script generator (or the compiler) would check for dups.... not intentionally from me, but I'll ~try to go thru the script and check for dups.
I've not purposely added any lines to the script other than that which would occur from the individual [AddFiles].
I do not recall EVER adding any Manifest files; I suggest that Any Manifest entries have been performed by InnoScript.
**
You may not be using the templates as you should (recommended) or modifying lines manually (not recommended). When you modify lines manually without using the templates to do the modification; you may forget or not type the lines the same each time leading to incorrect results and/or duplications.
**
We've not intentionally used any templates, and never intended to use any templates. The process was that we directed InnoScript to produce per the VBP, then we added the various app reference files (pdf's, txt, etc), then we selected [ADD] from the SxS so as to provide most secure use of the registered libraries, etc.
**
I don't see a database in your script but you have database modules in the script. If you are deploying a database in the {app} folder and it is deployed in the {pf}, {pf32}, {pf64} folders (not recommended) you will experience issues related to maintenance with the database.
**
There is no specific database in the script.
DB's are manufactured realtime via app generation &/or import.
This is a dynamic process and needs are constantly changed.
The primary DB driver is SQL however Jet and other via ADO are also offered in the app.
Note that the script Dependencies are generated per InnoScript.
**
Can't send any manifests as all have been lost.
This because InnoScript run using SxS caused app issues which were broken/severe (a number of apps including IDE would not launch, etc) and thus a system backup image was employeed.
InnoScript will not check for duplicates or add duplicate unless you have instructed it to do so in a template. InnoScript nor any compiler should check for duplicates for they are meaningless. Editing of the script should be done via a template not manually for results may vary and you may not remember where changes came from. I see the script and immediately know what changes were done manually.
I can see that the script was edited, there are lines commented out and added of which InnoScript would not ever do unless instructed to do so in a template; and since you state that you are not using the template function, these lines had to be added and commented out manually. Here is an example:
;must be XP or above OS:
;OnlyBelowVersion=,5.1.2600sp3
MinVersion=0,5.1.2600sp3
There is no way InnoScript would have done this. This should have been done on the main screen on the Versioning tab with the selection buttons. There was no reason to edit the script to get the proper results. Other such edits exist in the script. Once you start to do this you may not be able to tell who changed what or when it was changed.
InnoScript does add manifest files but not duplicate ones... We use InnoScript here everyday to create scripts for others as well as for our products we deploy including WinSxS deployments. We do not have any broken IDE or other such issues with WinSxS deployments. Perhaps if you could zip the deployment files along with the vbp and exe, I will run InnoScript with them to generate the appropriate script that should be generated and I guarantee the script would not look the same as the one you have and would not break ANY of our applications here.
Yes, I did comment out some lines because InnoScript had a problem with safe mode, or input file location, or some other etc.... I suggest not an issue for the subject analysis.
Also, some of the file names were changed prior to my post to you so as to protect some sensitive info.... again not critical to this analysis.
As far as duplicate manifest entry, perhaps a result of my input edit but, as u say, one will not recall
Anyway, duplicate manifest of same name is not functional... I'd call that an error, and thanks for pointing it out.
As far as breaking existing apps, it happens and is repeatable and takes me a few hours to recover via an image restore... I've already delineated with you one of the problems relative to DAO350.DLL as pertains to InnoScript re-registering at a different location and thus breaking VB6... you offered fix but it's manual & time consuming for all the dll's and offers error..... there are others... sorry but I've just been told I do not have time to go further, thus:
I thank you for your offer to do further analysis.... that must be sometime in future as time on this for me at present has again run out.
Bests & thank you for your support!
The offer was to create your script for you. All our applications on the web have WinSxS versions and something that bad would have surfaced by now on our development systems. This is why we offered to create your script for you at no cost for we want to see this issue that we have not seen before and we have a few applications out there with WinSxS versions created in InnoScript. We want to resolve this issue.
It occurred to me that if you are using your development machine to test with all sorts of malady's can happen such as the ones you mentioned. I would suggest that if you want to test on your machine that you use Microsoft's Virtual PC 2007 SP1 (http://www.microsoft.com/downloads/en/details.aspx?FamilyId=28C97D22-6EB8-4A09-A7F7-F6C7A1F000B5&displaylang=en&pf=true). You can start with a clean system each time and not have to worry about corrupting your development environment.
Thanks, But not doing Any Deployment tests on any Developemnt machines....& we do use Virtual Machines on the other test hardware.
It's the IDE, among some others, that breaks immediately after first run of InnoScript with SxS employed. Appears to me that these Breaks occur because InnoScript 'moves' some of the registrations when SxS is used.
Thanks again but my schedule precludes me from performing more testing at this time. thx!
OK, when you do get time; please make sure you download the latest version from the website to test with.
got it, thx, I'll notify you when more work is accomplished. Thank you for your support.