All, I contacted SAP support but this basically is some sort of configuration/environment issue rather than an actual SAP BO Postalsoft ACE software issue. I've taken several steps to verify that the software itself is functioning fine. Some specific interplay between SQL server/Windows/and the ACE software causes the software to "hang" when it's execute through SQL server VIA xp_cmdshell. Note that this methodology works fine in prior implementations using SQL server 2000/2005 and windows 2003 server. It's only in this new environment using SQL 2012 and Windows 2008 server R2 that we're experiencing this issue.
I'm hoping somebody in the community has seen this issue before and has an answer or even ideas for debugging.
I am unable to execute the SAP Business Objects Postalsoft ACE software
VIA MS SQL Server using xp_cmdshell functionality. The software
executes VIA all other methods either through the GUI (ACE Views) or
the command line pwace using the same template and input
files/data/commands. We've executed the software under the same
network account as the SQL server for testing as well as various other
network user accounts with no problems, it is only when the software is
executed VIA the SQL server xp_cmdshell method that it seems to "hang".
This is a new installation on a new virtual server. I am a new super
admin on this system and this is my first product request.
Win Server 2008 R2 Standard
MS SQL Server 2012 Standard
ACE version 8.00c.0200
Steps for Reconstruction
SQL server command shell executing ACE as follows:
exec
master..xp_cmdshell 'c:\pw\ace\pwace /a /lf:\usaf\firstlogic\temp\fl_3AE
EF26A_DCA9_41BC_AE76_8AD1B1A5C68F\fl_cass.log "f:\usaf\firstlogic\temp\f
l_3AEEF26A_DCA9_41BC_AE76_8AD1B1A5C68F\fl_cass_input.ace"'
When execute as above the software "hangs", when executed directly in
the windows command line (all environment and user account equal), the
job runs without issue.
c:\pw\ace\pwace /a /lf:\usaf\firstlogic\temp\fl_3AEEF26A_DCA9_41BC_AE76_
8AD1B1A5C68F\fl_cass.log "f:\usaf\firstlogic\temp\fl_3AEEF26A_DCA9_41BC_
AE76_8AD1B1A5C68F\fl_cass_input.ace"
Lastly I'll note that our DBA ran accross this MS KB article about COM permissions and we implemented the security changes outlined within for testing. This caused no change in the behavior of the app.
http://support.microsoft.com/kb/899965
Any help or information would be greatly appreciated!