Progress V9.1E, XP Pro SP2 Config
I have successfully integrated 4gl code (GUI or Char) that opens the OUTLOOK COM object in a NON DISPLAY mode and using the Redemption DLL COM toolset, I am able to bypass the OUTLOOK security prompts, and have its OUTLOOK generated draft message sent out via OUTLOOK (or an OUTLOOK/EXCHANGE combo (typically 3 to 7 sec delay till Outlook Process terminates).
My goal was to have our real time remote production data capture stations monitor system integrity issues, and via an appserver (asEmail) resident with the development toolkit, issue the out off tolerance email messages being sent via the call to the asSendRedemptionEmail.p procedure(avoiding Outlook having to be installed on all the production floor Client Workstations).
When I call the procedure directly in its appserver folder it works fine.
eg. RUN E:\appServers\asEmail\asSendRedemptionEmail.p.
When I try running it as:
RUN E:\appServers\asEmail\asSendRedemptionEmail.p ON SERVER hasEmail.
It returns the following info in the asEmail.server.log:
Application Server connected with connection id: 10.253.249.23::asEmail::3098::a6291236450642cf:690726:1188a839bc5:-7fcb. (8358)
-- TRACE: Non-PERSISTENT Procedure 'E:\AMCO-WRK\appServers\asEmail\sendEmailRedemption.p' START. (5498)
Procedure: 'asEmail\asSendRedemptionEmail.p' Line:181 Error occurred while accessing component property/method: Body.
Out of memory or system resources. Close some windows or programs and try again
Error code: 0x80020009 asEmail\asSendRedemptionEmail.p (5890)
Procedure: 'asEmail\asSendRedemptionEmail.p' Line:181 Unable to set com-handle property. (5677)
-- TRACE: Non-PERSISTENT Procedure END SUCCESS. (8397)
Application Server disconnected. (8360)
After trying to grasp how Progress spawns and runs an App Server Process, I have been following the path of trying have the AppServer spawn a standalone batch process as follows:
CMD /q/c "C:\PROGRA~1\PROGRE~1\bin\_progres.exe -b -ininame e:\prod\proof\ini\prswD-V91E-C-Prod-E.ini -p E:\appServers\asEmail\asSendRedemptionEmail.p"
and using an appserver 'test-asEmail.p' procedure that issues the following:
commandStr = 'E:\AMCO-WRK\appServers\asEmail\asSendRedemptionEmail.bat'.
OS-COMMAND VALUE(commandStr).
Thinking that this would spawn a free standing _progres.exe session and the code would run just like it does when I open a _progress.exe session on the XP desktop, and/or from a XP desktop Icon.
But alas the OS-COMMAND is totally ignored in the appserver call.
So to my fellow Progress Travelers, does anyone have some inspiration, explanations for my starting appserver project...........??????:biggrin::awink:
I have successfully integrated 4gl code (GUI or Char) that opens the OUTLOOK COM object in a NON DISPLAY mode and using the Redemption DLL COM toolset, I am able to bypass the OUTLOOK security prompts, and have its OUTLOOK generated draft message sent out via OUTLOOK (or an OUTLOOK/EXCHANGE combo (typically 3 to 7 sec delay till Outlook Process terminates).
My goal was to have our real time remote production data capture stations monitor system integrity issues, and via an appserver (asEmail) resident with the development toolkit, issue the out off tolerance email messages being sent via the call to the asSendRedemptionEmail.p procedure(avoiding Outlook having to be installed on all the production floor Client Workstations).
When I call the procedure directly in its appserver folder it works fine.
eg. RUN E:\appServers\asEmail\asSendRedemptionEmail.p.
When I try running it as:
RUN E:\appServers\asEmail\asSendRedemptionEmail.p ON SERVER hasEmail.
It returns the following info in the asEmail.server.log:
Application Server connected with connection id: 10.253.249.23::asEmail::3098::a6291236450642cf:690726:1188a839bc5:-7fcb. (8358)
-- TRACE: Non-PERSISTENT Procedure 'E:\AMCO-WRK\appServers\asEmail\sendEmailRedemption.p' START. (5498)
Procedure: 'asEmail\asSendRedemptionEmail.p' Line:181 Error occurred while accessing component property/method: Body.
Out of memory or system resources. Close some windows or programs and try again
Error code: 0x80020009 asEmail\asSendRedemptionEmail.p (5890)
Procedure: 'asEmail\asSendRedemptionEmail.p' Line:181 Unable to set com-handle property. (5677)
-- TRACE: Non-PERSISTENT Procedure END SUCCESS. (8397)
Application Server disconnected. (8360)
After trying to grasp how Progress spawns and runs an App Server Process, I have been following the path of trying have the AppServer spawn a standalone batch process as follows:
CMD /q/c "C:\PROGRA~1\PROGRE~1\bin\_progres.exe -b -ininame e:\prod\proof\ini\prswD-V91E-C-Prod-E.ini -p E:\appServers\asEmail\asSendRedemptionEmail.p"
and using an appserver 'test-asEmail.p' procedure that issues the following:
commandStr = 'E:\AMCO-WRK\appServers\asEmail\asSendRedemptionEmail.bat'.
OS-COMMAND VALUE(commandStr).
Thinking that this would spawn a free standing _progres.exe session and the code would run just like it does when I open a _progress.exe session on the XP desktop, and/or from a XP desktop Icon.
But alas the OS-COMMAND is totally ignored in the appserver call.
So to my fellow Progress Travelers, does anyone have some inspiration, explanations for my starting appserver project...........??????:biggrin::awink: