cancel
Showing results for 
Search instead for 
Did you mean: 

Agentry Server error - please contact your administrator (13)

CRVMANISH
Contributor
0 Kudos

Hello Experts,

I am using SQL as backend, i am getting following error in Agentry.

"Server error - please contact your administrator (13)"


How Agentry is connected to backend ,

while downloading data it gives error

Regards

Manish

Tags edited by: Michael Appleby

Accepted Solutions (0)

Answers (1)

Answers (1)

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Manish,

An error 13 when connected to a SQL backend will almost alwasy be an error in one of your queries.  If you haven't already check the events.log for the specific error message and also turn on your Backend-SQL log file (seperate file Yes) for the most detail.  Then when you try again the log file will have the exact query sent to the backend so you can review, cut/paste to a query tool and troubleshoot accordingly.

Without more details I can't really provide more assistance.

--Bill

CRVMANISH
Contributor
0 Kudos

Hello Bill

Thanks for reply, i know the setting.

I will send you the results.

Do we need to create Syclo users in SQL DB

Regards

Manish

CRVMANISH
Contributor
0 Kudos

Here is the log file

Regards

Manish

sravanthi_polu
Contributor
0 Kudos

Hi,

Please verify if the database is configured in system dsn.

Regards,

Sravanthi Polu

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Manish,

I don't see any error in the snippet fo the log file you attached.  Everything looks good in terms of the Agentry server initializing the connection to the database.  Can you transmit to generate the error and check again.

I would expect to see something similar to the following

2014/06/24 14:26:58.587:                 : 3 lines, 0 non-printing characters, 247 total characters

3: SA_DBMS_API_Error, vendor says:

>ERROR  102:42000 [Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near 'SycloCommoditiesUp'.

42000 [Microsoft][SQL Server Native Client 10.0][SQL Server]Statement(s) could not be prepared.

You can then see the exact SQL query that the server attempted to execute.  This allows you to spot errors or even copy and paste into your query tool (SQL Management Studio?) to attempt to execute there and confirm the problem.  Then you can go back into the Agentry editor and make the correction.

--Bill

CRVMANISH
Contributor
0 Kudos

Bill,

There is problem with my design i guess, i cannot see Transmit button.

Will let you know once i fix it.

Regards

Manish

bill_froelich
Product and Topic Expert
Product and Topic Expert
0 Kudos

Manish,

If you are using the ATE and forgot to create a transmit button, go into the Test Menu and select Force Transmit.  This will kickoff a transmit process to allow you to sync the client and pickup changes to correct the missing transmit button.

The other option is to reset the client and when you first login you will be prompted to connect to the server.  This should then generate the logs so you can see where the Error 13 is coming from.

--Bill