Intelligent Automation & Macro Software  

Go Back   Automation Anywhere, Inc. Forums > Products Zone > Automation Anywhere
Register FAQ Search Today's Posts Mark Forums Read

Automation Anywhere Post messages and questions related to Automation Software here.


Reply
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 06-24-2010, 10:35 PM
Brodie Brodie is offline
Junior Member
 
Join Date: Jun 2010
Posts: 2
Default Stored Procedure not completing successfully

I have a simple task setup to connect to a SQL database, run a stored procedure, then disconnect.


The stored procedure i am calling works successfully from within SQL Enterprise Manager, but fails within AA. I am using version 5.5.

I have tested this with other store procedures on the same database, and they work fine. The only difference i can see between the stored procedures is that the one which is failing takes about 6-10 minutes to run via SQL Enterprise Manager, vs. the other stored procedures which take seconds to run.

I have put time out options into the connection parameter and on the stored procedure task line, but this doesn't seem to make a difference.

No parameters are passed in the stored procedure, and the stored procedure name is sprdwloadcompany so does not have any of the known issues like commas or over 100 char that i can find in the forums.

Any ideas for tracking this down? As AA is only telling me to look at line 2 called Stored Procedure - not v. helpful.

Thanks for your help.
Reply With Quote
  #2 (permalink)  
Old 06-25-2010, 03:41 PM
forumsupport forumsupport is offline
Senior Member
 
Join Date: Apr 2007
Posts: 1,342
Default

Hello,

Did you try putting time (600 sec) in 'Timeout for the procedure' field of Database:Run Stored Procedure' command?

Hope that helps.
Reply With Quote
  #3 (permalink)  
Old 06-25-2010, 08:24 PM
Brodie Brodie is offline
Junior Member
 
Join Date: Jun 2010
Posts: 2
Default Timeout options already tested

Hi,
Yes i have put the maximum time out period i could into the optional timeout box in the stored procedure command, and have also tested passing a timeout value as part of the Connection string also.

Any other ideas?
Reply With Quote
  #4 (permalink)  
Old 06-28-2010, 01:55 PM
forumsupport forumsupport is offline
Senior Member
 
Join Date: Apr 2007
Posts: 1,342
Default

Hello,

This is strange as we have not experienced such issue before.

Is it possible for you to upload your stored procedure or upload the text format of procedure so we can look into it and try to reproduce the scenario at our end?

It would help us investigate further.
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT -7. The time now is 10:05 PM.


Powered by vBulletin® Version 3.8.6
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.0.0 ©2007, Crawlability, Inc.
Copyright © 2003-2011 Automation Anywhere, Inc. All rights reserved