Identifying Duplicate Transactions

re: Identifying Duplicate Transactions

David Musgrave — Tue, 02 Dec 2008 04:59:35 GMT

Posting from the Dynamics GP Blogster

http://dynamicsgpblogster.blogspot.com/2008/12/sql-mania-series-at-developing-for.html

re: Identifying Duplicate Transactions

David Musgrave — Sat, 06 Dec 2008 02:34:56 GMT

Posting from Vaidy Mohan's Blog

http://www.vaidy-dyngp.com/2008/12/davids-sql-series-identifying-duplicate.html

Identifying Duplicate Transactions

DynamicAccounting.net — Sun, 07 Dec 2008 22:00:53 GMT

I just wanted to take a second and highlight again David Musgrave's very useful SQL Scripts Series

re: Identifying Duplicate Transactions

Leslie Vail — Mon, 08 Dec 2008 11:29:16 GMT

As always an awesome addition to my bag of tricks. David you rock!

Identifying Duplicate Transactions

Mohammad R. Daoud — Thu, 11 Dec 2008 03:54:56 GMT

By David Musgrave http://blogs.msdn.com/developingfordynamicsgp/archive/2008/12/05/identifying-duplicate-transactions.aspx

Useful SQL Scripts Series

Microsoft Dynamics GP US Field Team blog — Thu, 11 Dec 2008 05:05:59 GMT

Based on the success of the "Resolving Security Issues in Dynamics GP" located here, Microsoft

re: Identifying Duplicate Transactions

Robert Cavill — Thu, 15 Jan 2009 06:46:00 GMT

There is a similar message you can get that refers to createTmpTable rather than createSqlTmpTable when dealing with financial series inquiry windows.

However, the same applies in that the stored proc mentioned does not actually exist, but is pass thru sql code that is causing the error.

"The stored procedure createTmpTable returned the following results" DBMS: 12, Microsoft Dynamics GP 0."

See KB 852594.

Error 12 possibly means the table cannot be created or accessed within the tempdb database.

re: Identifying Duplicate Transactions

cyboc — Mon, 19 Jan 2009 22:39:10 GMT

One of my users received a somewhat similar message when doing a Payables Transaction Inquiry in Dynamics GP 9 running on SQL Server 2000. The exact error was: "The stored procedure createSQLTmpTable returned the following results: DBMS: 12, Microsoft Dynamics GP: 0".

Searches of the CustomerSource knowledge base, the Dynamics community forums and Google have been fruitless. I don't know what DBMS error 12 means. I couldn't even find a reference to that error in the Books Online for SQL Server 2000.

Naively, we restarted Dynamics and tried the inquiry again. This time the inquiry worked. However, I would like to know more about what caused the error and how to permanently fix it or prevent it from happening. We tend to see it a few times a week, for a few users.

"The stored procedure createSQLTmpTable returned the following results: DBMS: 12" exceptions

Developing for Dynamics GP — Tue, 20 Jan 2009 07:00:56 GMT

Many of inquiry windows in Microsoft Dynamics GP have been optimized to leverage SQL Server to increase

"The stored procedure createSQLTmpTable returned the following results: DBMS: 12" exceptions

Developing for Dynamics GP — Tue, 20 Jan 2009 08:06:55 GMT

Many of inquiry windows in Microsoft Dynamics GP have been optimized to leverage SQL Server to increase

re: Identifying Duplicate Transactions

poWerRex — Tue, 03 Nov 2009 13:00:09 GMT

I found it very useful, specially in fixing those transactions with posting interruption problems.