Sage 100

 View Only
  • 1.  It seems something happened today on a working ins

    Posted 07-31-2013 14:25
    It seems something happened today on a working installation of MAS200v4.50.6. When running any Crystal Report in a non-legacy module the User is prompted to enter a company code, user id and password, if you don't the following error dialog pops. So far I've replaced the pvxsec32.dll, verified folder and file security, ensured firewalls are turned-off.


  • 2.  RE: It seems something happened today on a working ins

    Posted 07-31-2013 14:29
    Did you try reinstalling the workstation (and make sure that the User Account Control is set to Never Modify so that the MAS workstation installs properly)?


  • 3.  RE: It seems something happened today on a working ins

    Posted 07-31-2013 14:31
    Yes, at the moment I'm changing the Data Execution Prevention setting and rebooting.


  • 4.  RE: It seems something happened today on a working ins

    Posted 07-31-2013 15:03
    OK, changing DEP did nothing to resolve. Any ideas?


  • 5.  RE: It seems something happened today on a working ins

    Posted 07-31-2013 15:30
    Did you replace file from a backup or from another 4.5 instance? I had this same error couple days ago and I replaced from my copy of 4.50. Worked great. All users had issue though


  • 6.  RE: It seems something happened today on a working ins

    Posted 07-31-2013 15:42
    Did you add a parameter to the report that pulls a selection list from MAS? That will cause this...


  • 7.  RE: It seems something happened today on a working ins

    Posted 07-31-2013 16:39
    The problem is resolved. Turns out the pvodbsec.ini file went missing from the /MAS90 Folder. This file points Crystal (or any other odbc data call) to look to the pvxsec.ini for instructions. When it goes away the system fails over to the old MAS log-on screen and pass-thru security doesn't seem to work. Bottom line...don't loose this file.


  • 8.  RE: It seems something happened today on a working ins

    Posted 07-31-2013 16:42
    Claudia: Yes, this did affect all users and I did replace the pvxsec32.dll from a know good back-up. However with the pvodbcsec.dll missing we lost the pointer to pvxsec.dll. We haven't identified how this got lost, but it doesn't bode well.