Sage 300

Welcome to the Sage 300 Support Group on Community Hub! Available 24/7, the Forums are a great place to ask and answer product questions, as well as share tips and tricks with Sage peers, partners, and pros.

Deadlock victim. [Database vendor code: 1205]

Posted By Gopi Thulasidass over 6 years ago

The problem occur when user try to print transaction listing report

Anyone knows why is this problem occurs?

Top Replies

Jay Converse Acumen over 6 years ago in reply to Gopi Thulasidass +1

Since it's consistent, run RVSPY and SQL profiler, reproduce the error, and analyze the logs. Something is wrong with your SQL configuration.

Jay Converse Acumen over 6 years ago

Version? PUs? SQL Version? OS? Does it happen consistently? How many users? How many servers?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Gopi Thulasidass over 6 years ago in reply to Jay Converse Acumen

Version: Sage 300 6.0A (Sage ERP ACCPAC 500) (Build 2)

PU: Product Update

SQL Version: MS SQL server 2012

OS: Windows server 2008 R2

Yes It does happen consistently. One server for 10 users. The report is standard not customized.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel
Jay Converse Acumen over 6 years ago in reply to Gopi Thulasidass

Since it's consistent, run RVSPY and SQL profiler, reproduce the error, and analyze the logs. Something is wrong with your SQL configuration.
Cancel
Vote Up +1 Vote Down

Sign in to reply

Cancel
Gopi Thulasidass over 6 years ago in reply to Jay Converse Acumen

Hi Jay, Thanks for the reply. The issue was in ODBC connection.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Cancel

Sage 300

Deadlock victim. [Database vendor code: 1205]

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING