InstallAware

Hi,

I created a web deployment on local environment and everything work great.
After we try to create another web deployment on customer environment, we found its not worked.
We put the update script and Web update installer into customer server.
As mentioned, the update script is what I wrote as below:


The scenario are:
1. They are successful upgrade version into 4.0.88.0
2. Recently there another upgrade which version 4.0.88.1
3. I have to modify update script to cater for version 4.0.88.1

4. I have to put new update script and exe into customer server.
5. Normally I will using Internet Explorer download update script and installer to ensure web update is workable.
6. The both files successful download
7. I found very weird thing is the update script content are different and look outdated which is like

8. Customer unable update newest version 4.0.88.1 due of script still pointing on old version which is (4.0.88.0)
FYI, the customer server using windows server 2012 and using IIS 7.

Does that related problem on my script or IIS setting?

Found out the update script is located: C:\Inetpub\wwwroot\ParkwayShenton\Update\updates.ini
As you can see there are big capital on the folder while my update_server variable pointing all small capital case folder name, which unable to find next version

1. Does it mean my UPDATE_SERVER variable require to put big capital which same name as folder, in order get correct next version upgrade?
2. No matter small or big capital the UPDATE_SERVER will still able find the update script?

Dear Danieltan,

in all honesty it's not clear to me which are the exact steps you used to replicate the issue you seem to have.

Anyway for sure, the problem cannot be caused by the capital letters with the folder name.

First because a Microsoft operating system is case insensitive with file names or folder names.
This means that it will read a capital letter in the same way it will read a lowercase letter.

Second because (for what I can understand by your description) your first update gets applied correctly.

If you have any chance to share with me a very minimal project that replicates the issue, I'll try to have a look.
You may contact me at: support@installaware.com, in case you don't want to publish sensitive information on the forum.

Regards

Hi,

These few day, I tried to reproduce the problem of script content may different from the web server (all of files consists of updates.ini and installer are hosted under IIS 7)
Found interesting stuff.

1. To enable web update, require put the files in web server and require host in IIS? (refer on below screenshot)

2. Does we require put as folder type or require convert as application type?

3. What I found, using local machine not matter folder or application type it will show accurate content for updates.ini but out of curious the client machine does not display updates.ini content accurate once the files is host under application type

Dear Danieltan,

I don't understand why you want to use an application instead of a folder.
If you are using IIS, It's just necessary TO USE a STANDARD folder and this (the "Update" folder) has to be located under your Website.

Of course the folder contents must be accessible and this can be easily verified, trying to manually download the files via browser. Did you try it?

Regards