AdvancedInstaller on multiple Build-Servers

[LuWa]

Hi.

I am using AdvancedInstaller 12.4.2
We duplicated our Build-Server 3 times.
When the AdvancedInstaller Task runnig at the same time on multiple Servers (2 or more) it hangs up and runs in a Timeout (after 1:30 Hours the Build-Server kills the process).
Can you imagine what the problem is?
Should we update to the newest version to solve the problem?

Dears, Lukas

[Daniel]

Hello Lukas,

I'm not sure if I fully understood your what is your build scenario. Do you run multiple Advanced Installer build operation at the same time on the same machine? If so, this may happen if the concurrent builds try to access the same resources from disk at the same time.

In this case you should try to trigger again the build operation when failed.

Let us know if this helped, otherwise please give us more details about your build scenario.

All the best,
Daniel

[LuWa]

Hi Daniel.

I use ist at the same time on different machines.
I dont know why the process hangs up. maybe the signing process?

Regards,
Lukas

[LuWa]

Here you can see the output of my server:

2018-02-20T19:46:49.3565664Z Die folgende Befehlszeile wird ausgeführt. (workingFolder = E:\9\s)
2018-02-20T19:46:49.3565664Z C:\Program Files (x86)\Caphyon\Advanced Installer 12.4.2\bin\x86\AdvancedInstaller.com /rebuild "PPINST\PrintplusVerlagServer\PrintplusVerlagServer.aip"
2018-02-20T19:46:49.3565664Z Error message highlight pattern:
2018-02-20T19:46:49.3565664Z Warning message highlight pattern:
2018-02-20T19:46:50.7159982Z Checking builds status... done.
2018-02-20T19:46:50.7159982Z Build required.
2018-02-20T19:46:50.8253787Z [ DefaultBuild ]
2018-02-20T19:46:50.8722528Z Building package (de):
2018-02-20T19:46:50.9350397Z C:\PrintplusVerlagServer\PrintplusVerlagServer Setup 2018.1.0.0.exe
2018-02-20T20:45:30.2611008Z Preparing files...


Stopped at: 21:45:32

[LuWa]

Sometimes i get the following error:

2018-02-22T13:17:13.6698747Z Creating CAB file(s)... [SEH_AV_READ_BADPTR] ACCESS_VIOLATION (0xc0000005) at address [0x74c73043]
2018-02-22T13:17:13.6698747Z Advanced Installer 12.4.2 build 66135
2018-02-22T13:17:13.6854895Z *** Stack Trace (x86) ***
2018-02-22T13:17:13.6854895Z [0x74c73043] ASN1BERDecExplicitTag()
2018-02-22T13:17:13.6854895Z [0x74057e54] CertFreeCertificateChainList()
2018-02-22T13:17:13.6854895Z [0x74c733a9] ASN1_Decode()
2018-02-22T13:17:13.6854895Z [0x73fcf5af] CryptGetDefaultOIDFunctionAddress()
2018-02-22T13:17:13.6854895Z [0x7404f0af] CryptImportPKCS8()
2018-02-22T13:17:13.6854895Z [0x7404c9ed] PFXIsPFXBlob()
2018-02-22T13:17:13.6854895Z [0x013b9696] -----
2018-02-22T13:17:13.6854895Z [0x013b9e7c] -----
2018-02-22T13:17:13.6854895Z [0x00d65a3b] -----
2018-02-22T13:17:13.6854895Z [0x00d60000] MODULE_BASE_ADDRESS

[Daniel]

Hello,

I'm not sure what could cause these errors, but as a try you can change the timestamp server into your project. Just open your setup project, go to "Digital Signature" page and set the "Time stamp URL" field to use another timestamp server.

All the best,
Daniel

[LuWa]

I still have the same problem with another timestamp-URL:

2018-02-23T19:31:52.8536184Z Die folgende Befehlszeile wird ausgeführt. (workingFolder = E:\4\s)
2018-02-23T19:31:52.8536184Z C:\Program Files (x86)\Caphyon\Advanced Installer 12.4.2\bin\x86\AdvancedInstaller.com /rebuild "PPINST\PrintplusVerlagServer\PrintplusVerlagServer.aip"
2018-02-23T19:31:52.8536184Z Error message highlight pattern:
2018-02-23T19:31:52.8536184Z Warning message highlight pattern:
2018-02-23T19:31:54.1191328Z Checking builds status... done.
2018-02-23T19:31:54.1191328Z Build required.
2018-02-23T19:31:54.2128467Z [ DefaultBuild ]
2018-02-23T19:31:54.2284780Z Building package (de):
2018-02-23T19:31:54.2440984Z C:\PrintplusVerlagServer\PrintplusVerlagServer Setup 2018.1.0.0.exe
2018-02-23T20:41:37.4947423Z Preparing files...

Stopped at: 21:41

[Daniel]

Hello,

When the build hanging occurs could you just simply launch into your Internet Explorer web browser the timestamp URL and see if the timestamp server can be reached? Usually you should get a message like: "You have reached the ... timestamp".

Maybe there is really a problem with the timestamp request being posted from your network.

Also, for testing purposes only, just try to install our latest version of AI (14.6) on your build server and see if this helps? We have added several improvements into the digitally signing feature since AI 12.4.2, but I cannot say for sure if this will be useful for your case. You will have to test it to see how it works against your test case.

All the best,
Daniel