Sage 100

2014 PU3. Windows server 2012. Converted all forms. Trying to preview a sales order and getting an error message: ""The keyset is not defined."". Verified database.. up to date.

Try a generic form, try updating UDF fields

UDF's have been problematic for me in the past..... VI's don't work unless you remember to update them so @WayneSchulz thought is a great place to start.

Do you get a more useful error if you try running from within Crystal instead of from Sage?

No luck. Probably going to have to call Sage Monday. Same error with generic form. Updated udfs. Updated and rebuilt custom screens (again). Re-installed workstation setup. Ran client as administrator. UAC is off. @BethBowers trying to print sales orders so don't know how to run from within Crystal.

@DougHiggs - preview from some place you CAN preview a sales order. While order is still open, rename SO_SAlesOrderWrkXXXXXXXXXXXXX.M4T to SO_SalesOrderWrk.M4T. Now you can open on this machine in Crystal and try previewing.

Have a peek at this: http://sagecity.na.sage.com/support_communities/sage100_erp/f/92/t/75226.aspx

Thanks Wayne. I have already seen that (Googled the error message). Tried removing all tgypes compatibility, adding other types of compatibility such as Win 7.... nothing works.

Did you get this resolved?

Not yet... will call Sage today.. I had bigger fish to fry yesterday at the same client... f'n workstation install wouldn't connect. tried everything . after 5 hours finally checked the spawn tasks box in user maintenance and that magically worked.. going back onsite this morning.

Also going to try @BethBowers suggestion first.

Update...Solved.... I was on site yesterday and worked on this issue for another 4 hours before finally figuring it out..... this was a tough nut to crack.. what really puzzled me was when I started installing the client workstations they were getting the same error... ""the keyset is not defined"" whenever they tried to print.... the resolution was close at hand all along @WayneSchulz had the link to Ronnie Aspe's solution above. The difference was that the Windows XP SP2 compatibility was on the mas90\home\pvxwin32.exe program, not on the program icon which is where I looked. I have no idea how pvxwin32.exe compatibility got changed. Iif you click Wayne's link above you will see the KB update from yesterday at the bottom of the thread.

Ugh......... Hope you didn't lose your shirt on this one!!!!!