batch recovery failure

[Jacob Raymond]

Hi,

I posted a payables batch and it gave me an error and instructed me to use
batch recovery. When I tried to recover the batch I get the following message:

The stored procedure icpmValidateIC returned the following results: DBMS:
512, Microsoft Dynamics GP: 0.

Anybody know what I have to do next?

Thanks.

[Mariano Gomez]

This is telling you that the stored procedure in question executed an action
that resulted in more than one value being returned -- typically a SELECT
statement that attempts to assign its resultset to some variables, something
like SELECT @x = foo_column from footable. In this case the SELECT is
returning more than one value that is trying to be assigned to @x throwing an
error 512.

Unfortunately, there is no easy fix for this without knowing the details of
your environment, but I would try to run the Automated Solutions designed to
deal with batch issues:

Dynamics GP v10 (ClearBatchActivity10_v1.msi in System Manager's section
https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions/automatedsolutionsR10.htm

Dynamics GP v9 (Clear Batch Activity v9.2.msi in System Manager's section
https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions/automatedsolutions9plus.htm

Once you have recovered the batch, run a batch edit list looking for any
error messages on transactions that would prevent the batch from posting, for
example, close fiscal periods, etc.

If you cannot seem to find the problem, move the transactions from the
damaged batch to a new batch. At this point, I would also clear the
wkPostingValidationState table and the pJournal table located under your
company database (MAKE A BACKUP AND HAVE EVERYONE EXIT THE SYSTEM BEFORE
TRYING THIS).

If this still does not resolve the issue, then make sure you are on the
latest service pack for your version of Dynamics GP.

If after applying the service pack you are still experiencing the issue,
turn on a DEXSQL.LOG. You can install the new Support Debugging Tool which
you can obtain from your partner. In turn, they can download from
PartnerSource. In any case, the DEXSQL.LOG will allow you to pinpoint the
specific SQL transaction that is causing the issue.

Last but not least, if none of the above resolves the issue, delete and
re-enter the batch.

Good luck,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com

Post by Jacob Raymond
Hi,
I posted a payables batch and it gave me an error and instructed me to use
512, Microsoft Dynamics GP: 0.
Anybody know what I have to do next?
Thanks.

[Jacob Raymond]

Thanks Mariano,

We are running GP 10 professional version 10.00.1061 on MS SQL 2005
9.00.3042.00 (X64). The OS on the server is running MS windows 2003 R2 64
bit. All the client systems are running windows vista with the latest service
pack.

I did try the Automated Solutions related to batch issues but that didnt
solve the problem. I am still stuck with a batch I cant recover. Would it be
safe to delete the entries from the tables using sql?

Regards.

Jacob.

Post by Mariano Gomez
This is telling you that the stored procedure in question executed an action
that resulted in more than one value being returned -- typically a SELECT
statement that attempts to assign its resultset to some variables, something
error 512.
Unfortunately, there is no easy fix for this without knowing the details of
your environment, but I would try to run the Automated Solutions designed to
Dynamics GP v10 (ClearBatchActivity10_v1.msi in System Manager's section)
https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions/automatedsolutionsR10.htm
Dynamics GP v9 (Clear Batch Activity v9.2.msi in System Manager's section)
https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions/automatedsolutions9plus.htm
Once you have recovered the batch, run a batch edit list looking for any
error messages on transactions that would prevent the batch from posting, for
example, close fiscal periods, etc.
If you cannot seem to find the problem, move the transactions from the
damaged batch to a new batch. At this point, I would also clear the
wkPostingValidationState table and the pJournal table located under your
company database (MAKE A BACKUP AND HAVE EVERYONE EXIT THE SYSTEM BEFORE
TRYING THIS).
If this still does not resolve the issue, then make sure you are on the
latest service pack for your version of Dynamics GP.
If after applying the service pack you are still experiencing the issue,
turn on a DEXSQL.LOG. You can install the new Support Debugging Tool which
you can obtain from your partner. In turn, they can download from
PartnerSource. In any case, the DEXSQL.LOG will allow you to pinpoint the
specific SQL transaction that is causing the issue.
Last but not least, if none of the above resolves the issue, delete and
re-enter the batch.
Good luck,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com

Post by Jacob Raymond
Hi,
I posted a payables batch and it gave me an error and instructed me to use
512, Microsoft Dynamics GP: 0.
Anybody know what I have to do next?
Thanks.

...

[Jacob Raymond]

I forgot to add, we are using the Analytical Accounting module too.

Regards.

Jacob.

Post by Mariano Gomez
This is telling you that the stored procedure in question executed an action
that resulted in more than one value being returned -- typically a SELECT
statement that attempts to assign its resultset to some variables, something
error 512.
Unfortunately, there is no easy fix for this without knowing the details of
your environment, but I would try to run the Automated Solutions designed to
Dynamics GP v10 (ClearBatchActivity10_v1.msi in System Manager's section)
https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions/automatedsolutionsR10.htm
Dynamics GP v9 (Clear Batch Activity v9.2.msi in System Manager's section)
https://mbs.microsoft.com/customersource/support/selfsupport/automatedsolutions/automatedsolutions9plus.htm
Once you have recovered the batch, run a batch edit list looking for any
error messages on transactions that would prevent the batch from posting, for
example, close fiscal periods, etc.
If you cannot seem to find the problem, move the transactions from the
damaged batch to a new batch. At this point, I would also clear the
wkPostingValidationState table and the pJournal table located under your
company database (MAKE A BACKUP AND HAVE EVERYONE EXIT THE SYSTEM BEFORE
TRYING THIS).
If this still does not resolve the issue, then make sure you are on the
latest service pack for your version of Dynamics GP.
If after applying the service pack you are still experiencing the issue,
turn on a DEXSQL.LOG. You can install the new Support Debugging Tool which
you can obtain from your partner. In turn, they can download from
PartnerSource. In any case, the DEXSQL.LOG will allow you to pinpoint the
specific SQL transaction that is causing the issue.
Last but not least, if none of the above resolves the issue, delete and
re-enter the batch.
Good luck,
--
MG.-
Mariano Gomez, MIS, MCP, PMP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com
The Dynamics GP Blogster at http://dynamicsgpblogster.blogspot.com

Post by Jacob Raymond
Hi,
I posted a payables batch and it gave me an error and instructed me to use
512, Microsoft Dynamics GP: 0.
Anybody know what I have to do next?
Thanks.

...