Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Get/Change Operation o...
Microsoft Dynamics GP (Archived)

Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data

(0) ShareShare
ReportReport
Posted on by erowden 727

I recently upgraded from GP 10.00.1237 to GP 12.00.2038.

1.) Upgraded to 10.00.1868 and ran utilities

2.) Users worked in that environment for 1 day

3.) Installed GP 2013R2

4.) Applied the MicrosoftDynamicsGP12-KB3102154-ENU.msp (year-end update)

5.) Ran Utilities

I did not have any errors in that process, however, the error message "Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data" occurs when posting a check batch and when you select a vendor in the 1099 vendor details maintenance. 

Was my upgrade process incorrect or is there some other issue that anyone is aware of?

*This post is locked for comments

  • Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data

    Thanks Jarrod for the information.

    One caution is that we do not want to drop and re-create the table via SQL Maintenance unless the table has no data in it. The reason for this is SQL Maintenance will only re-create the table, it will not keep data intact.

    To re-create a table with data intact, we recommend using the 'Toolkit' from the Professional Services Tools Library (PSTL) for Dynamics GP, which allows you to re-create the table with data intact.

    Thanks again.

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data

    Hi Sheila,

    I got this same error first posting check batches and then using batch recovery.  After working with support from my MS partner, I found that rebuilding stored procedures on "PM 1099 Setup Files" didn't work for me either.  They had me do the rebuild on "Purchasing 1099 Period Detail" which fixed my problem.  Actually I did a SQL backup of PM00204 first and then in SQL Maintenance did a Drop Table, Create Table, Drop Auto Procedure, Add Auto Procedure.  I went back to SQL and restored data to the table before proceeding.

    Hope that helps.

  • Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data

    Hello Sheila,

    I would run a dexsql.log to find out which procedure is actually causing the 'table definition' error, if that is what you're getting when printing a 1099.

    It may not be the zDP_PM00204SS_2 procedure, which is why re-creating it didn't fix your issue.

    Thanks,

    Derek

  • Sheilajr Profile Picture
    Sheilajr 745 on at
    RE: Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data

    Derek - the re-creating of the stored procedures did not resolve my error.  I attempted and when I print a 1099 edit list I get the same error message.  If you have any other ideas I'm open to them.

  • Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data

    Yes, the 'Number of Results' error normally means that the table doesn't have the exact structure that the stored procedure is expecting, when it's being run, causing this error, or vice versa.

    By re-creating the stored procedure, it corrected it to expect the table structure of the PM00204 table and thus resolved the error.

    Thanks again for updating this to let everyone know the resolution.

    Have a great day.

  • erowden Profile Picture
    erowden 727 on at
    RE: Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data

    The only additional info in the "More Info" window was "Number of Results column doesn't match table definition".  However, I believe I have since narrowed it down (at least what occurs when trying to post the check batch) to the stored procedure zDP_PM00204SS_2 that updates table PM00204 (for which a new column was added in the version .2038 year-end update).   I ended up running the SQL Maintenance >> SBM01 >> PM 1099 Setup File>> Drop AutoProcedure, Create Auto Procedure.  That did seem to solve it.

  • Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Get/Change Operation on table pm1099PeriodDtl failed accessing SQL data

    Hello Liz,

    When you get this Get/Change error, does it show a 'More Info' button? If so, click that and add the 2nd part of this error, which will say something like 'Invalid column xxxxx' or something like that. That will help us determine what the actual cause of the error is, as the Get/Change error by itself doesn't really tell us anything other than the pm1099PeriodDtl table name.

    Thanks,

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,401 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans