The error said: The Stored Procedure createSQLTmpTable returned the fo

[ucfperson]

The error said: The Stored Procedure createSQLTmpTable returned the following results: DBMS: 12 Great Plains: 0


We are running SQL Server 2000sp3a as a backend

Someone recomended the below link, but I don't have a login. Can someone help me out if you know the solution or have access.

Here is the URL:

https://mbs.microsoft.com/knowledge...NWWSOMPXOTYVZOYZPLVOTWXQZPRQLUVMRRZMWUNPQMULZ

 

[jymm]

text from that link - your partner should be able to get you validated for the sign on... hopefully this is the problem that you were encountering...

next time - make sure you tell us which version of GP and version of SQL since sometimes it does make a difference.

----
TechKnowledge Content
SYMPTOMS

"The stored procedure createSQLTmpTable returned the following results,
DBMS: 12 Great Plains: 0." occurs when selecting a Vendor in Vendor Inquiry.

CAUSE

This error can occur if the PM Keys are missing or corrupt.

RESOLUTION

To resolve this error, re-create the PM Keys.

Microsoft SQL Users

1. Make a full backup that can be restored to should undesirable results occur.
2. Have all users exit Great Plains.
3. Click Start, Click Programs, Click Microsoft SQL Server, and then Click Query Analyzer.
4. From the database drop-down list, select your Company database.
5. Type the following script in the query pane.

delete PM00400

6. Launch back into Great Plains.
7. Click File, Click Maintenance, and then Click Check Links
8. Under Series, select Purchasing.
9. In the file list, select Payables History Logical and click Insert and then select Payables Transaction Logical and then click Insert.
10. Click OK.
11. When prompted, select Print to Screen for the Error Log Report.


Ctree and Pervasive Users

1. Make a full backup that can be restored to should undesirable results occur.
2. Have all users exit Great Plains.
3. Browse to your Dynamics folder, expand the Company folder, and then expand the purchase folder.
4. Right click PM00400.*, click Rename, and then rename the PM00400.* to PM00400.old
5. Launch back into Great Plains.
6. Click File, Click Maintenance, and then Click Check Links
7. Under Series, select Purchasing.
8. In the file list, select Payables History Logical and click Insert and then select Payables Transaction Logical and click Insert.
9. Click OK.
10. When prompted, select Print to Screen for the Error Log Report.

Warning If you cannot successfully re-create your PM Keys, do not continue working in the system because future documents may become corrupted. If your PM Keys do not re-create successfully, you will receive an error message (the message text may vary) and you will not receive an error log.




This article was TechKnowledge Document ID: 32611

--------------------------------------------------------------------------------

APPLIES TO
• Microsoft Business Solutions–Great Plains Payables Management, when used with:
Microsoft Business Solutions–Great Plains 7.5
Microsoft Great Plains Dynamics 7.0
Microsoft Great Plains eEnterprise 7.0


Back to the top

----

 

[VictoriaYudin]

I have also seen this error come up when there is no problem at all with the keys tables. Often it is a connectivity issue.