Sage 100

 View Only
  • 1.  [Providex][ODBC Driver][PVKIO] Logon Failed.This

    Posted 04-04-2012 04:50
      |   view attached
    [Providex][ODBC Driver][PVKIO] Logon Failed. This error displays when accessing any BIE in MAS 200 4.5 PU3 (either on server or TS session). I've seen threads on this topic for Crystal Reports, but all reports print fine. Only BIE is affected. Thoughts?


  • 2.  RE: [Providex][ODBC Driver][PVKIO] Logon Failed.This

    Posted 04-04-2012 05:27
    But no other workstation? Sounds like security or setup though I have no details.


  • 3.  RE: [Providex][ODBC Driver][PVKIO] Logon Failed.This

    Posted 04-04-2012 06:04
    All workstations. Will try launching it using local admin account (to see if it's rights related).


  • 4.  RE: [Providex][ODBC Driver][PVKIO] Logon Failed.This

    Posted 04-04-2012 06:14
    Did they set up the UNC path one level above the MAS90 folder?


  • 5.  RE: [Providex][ODBC Driver][PVKIO] Logon Failed.This

    Posted 04-04-2012 09:27
    Yes.


  • 6.  RE: [Providex][ODBC Driver][PVKIO] Logon Failed.This

    Posted 04-04-2012 12:44
    I don't know if this is related but i recently had a similar error when running crystal reports on a citrix box and Alnoor suggested i rerun workstation setup from a terminal session and make sure we answered yes to the question is this being run from a terminal session because it wrote a setting to the registry. i think this could also be a path issue. See Alnoor's post regarding MAS200 path issues and admin accounts when running as a service.


  • 7.  RE: [Providex][ODBC Driver][PVKIO] Logon Failed.This

    Posted 04-11-2012 15:12
    I finally logged a case. Sage is able to duplicate... somewhat. They don't get the error, but their BIE views are blank. More to follow. Seems to be working fine in MAS 90 mode, but not MAS 200.


  • 8.  RE: [Providex][ODBC Driver][PVKIO] Logon Failed.This

    Posted 04-16-2012 14:08
    After several hours of trying this and that, I noticed that MAS was launching in XP Compatibility mode. Once disabled, error went away. MAS 200 4.3 on same server (2008 R2) works fine in compatibility mode. Appears that only 4.5 (all PU's) has this issue.