We're using a webserver to update all our applications with AppSync.
With several applications (FruityLoops, FLstudio, DFMA 9.3, Rhinoceros) we're encountering problems with the use of the AppSync functionality.
The applications will not start when AppSync is turned on. We get different error-messages for different applications.
When we turn off AppSync the problems are not occuring. Since Appsync is vital for updating our packages it is a big concern to us.
Can anyone help us out?
Hey Saxion,
Can you start by providing us a little more information? Are you starting the applications locally or over a network share? Are you using IIS for the AppSync update server (what location did you provide?). How are the updates named? What are examples of error messages that you are receiving?
Bye,
Tim
After authenticating users can download virtual applications from a Linux Apache webserver. They start the application locally.
The AppSync-server is another Linux Apache webserver which for the moment can only be used when inside the Saxion buildings (Wifi or Lan).
Standard we provide an updatepath for every application: AppSyncURL=https://appsync.server.nl/folder/app.exe
The applications mentioned (FruityLoops, FLstudio, DFMA 9.3, Rhinoceros) crash when the appsync functionality is on, no mather if there's an update available or not.
For the application DFMA 9.3 we get this error message:
"Design for Assembly has encounterd a problem and need to close. We are sorry for the inconvencience"
Sometimes we get a dumpfile which is generated by the application, they don't really help, and sometimes a general error message like "The application has generated an error and needs to close".
When we turn off the appsync mechanism (;AppSyncURL=) the problem is gone.
It looks like the mentioned applications somehow can't handle appsync.
I'm not looking for a direct solution to our problem with these applications but I'd like to know if anyone has encountered problems like these before with these or other applications.
That doesn't mean that a solution is not welcome.
Erik van Kuik
Saxion
I have kinda seen similar thing happen when AppSyncExpirePeriod=0d in older versions of ThinApp when the package fail to find/access the upgrade path. I believe this was resolved in newer version of ThinApp.
I have as well documented the AppSync process as well most seen configuration problems with the latest version at my blog at:
Hope this help someone who still hit this old forum post.
Regards,
Eiad Al-Aqqad
http://www.VirtualizationTeam.com
