Automic Workload Automation

  • 1.  Microsoft SQL Interface

    Posted Feb 07, 2017 11:32 AM
    Hi All

    I'm new here.  We at Lowell got Automic 11 in November 2016. I've had the Basic training course and have now got some experience with Automic. Nothing clever yet. I'll apologise for the stupid questions in advance.

    We're trying to connect a job object to a MSSQL database.  We have a connection object that tells me "Connect test was Successful" so I was expecting happy times but when I try and run a simple SQL select statement I get the following message.
    "(RunID '0001084718') on Host 'SQL01' aborted (return code='0000000102').  Remote status=Waiting for Database and the task fails"

    Anyone got any ideas what this means & how to fix it.

    TIA



  • 2.  Microsoft SQL Interface

    Posted Feb 07, 2017 04:22 PM
    I remember of an issue I had in quite the same situation but not what caused this :-(

    can you try defining a login end entering DB Server, DB name etc. manually within the SQL JOB- bypassing the CONN object?


  • 3.  Microsoft SQL Interface

    Posted Feb 10, 2017 11:04 AM
    Hi Wolfgang

    It looks like the issue is to do with Windows Authentication users.  The DBA has set up a user4 with SQL Authentication and it's working now.

    Now to work out how to call a stored procedure.....


  • 4.  Microsoft SQL Interface

    Posted Feb 10, 2017 01:30 PM
    Hi Mick

    Yeah that it! It was the mixed mode authentication I stumbled over....
    Thanks for posting/reminding me :-)

    For your stored procedure topic, possibly this can help:
    https://community.automic.com/discussion/5191/how-to-execute-a-sql-server-stored-procedure-from-a-sql-job

    and another hint, there are some technical articles (and Known Errors as well) at the support portal support.automic.com (logon necessary, credentials are the same as for community) maybe there are some which can help you.

    good luck! :-)


  • 5.  Microsoft SQL Interface

    Posted Feb 10, 2017 02:33 PM
    I can run a SQLServer stored procedure by prefixing it with "exec".


  • 6.  Microsoft SQL Interface

    Posted Feb 13, 2017 06:43 AM

    Cheers guys.

    I managed to get it running stored procedures last thing on Friday, so onto the next issue now, accessing the returned values.....



  • 7.  Microsoft SQL Interface

    Posted Feb 13, 2017 12:00 PM
    Do you need UC4 to access the returned values?  To do this, typically I would write enough SQL to cause the results to be displayed onto a report, and then I'd write some post-process script to capture the data off of that report.