Here are links to a special pre-release update of A5V11:
http://downloads.alphasoftware.com/a...full_patch.exe
http://downloads.alphasoftware.com/a...rver_patch.exe
This test build is specifically for people who are getting an 'a5wui' error message when trying to print a PDF report in a Web Application.
The 'a5wui' error is thrown when Alpha Five tries to bring up a message box. Any type of UI is illegal in a web application.
Alpha Five SHOULD not be trying to display any UI when printing in a Web app, but obviously, in some cases - which we think are report specific - it is.
We don't yet understand what is causing A5 to want to display any type of UI because we have never been able to set up our own test cases that duplicate any problem.
Howerver, in this test build, if A5 tries to display any type of UI, the command is ignored, and instead a message is written to the trace log indicating why an attempt has been made to display UI.
If you are experienced this problem, can you please download and install this test build.
Go to the Application Server control panel, Logging tab, and make a note of where the trace log files will be written.
Run your app. Can you now print?
If yes, can you then go to the Trace Log folder and send us the file that was written there.
http://downloads.alphasoftware.com/a...full_patch.exe
http://downloads.alphasoftware.com/a...rver_patch.exe
This test build is specifically for people who are getting an 'a5wui' error message when trying to print a PDF report in a Web Application.
The 'a5wui' error is thrown when Alpha Five tries to bring up a message box. Any type of UI is illegal in a web application.
Alpha Five SHOULD not be trying to display any UI when printing in a Web app, but obviously, in some cases - which we think are report specific - it is.
We don't yet understand what is causing A5 to want to display any type of UI because we have never been able to set up our own test cases that duplicate any problem.
Howerver, in this test build, if A5 tries to display any type of UI, the command is ignored, and instead a message is written to the trace log indicating why an attempt has been made to display UI.
If you are experienced this problem, can you please download and install this test build.
Go to the Application Server control panel, Logging tab, and make a note of where the trace log files will be written.
Run your app. Can you now print?
If yes, can you then go to the Trace Log folder and send us the file that was written there.