Sage 100

 View Only
  • 1.  Client running MAS 200 SU 12 or so. XP workstatio

    Posted 08-05-2011 09:41
      |   view attached
    Client running MAS 200 SU 12 or so. XP workstation SU3. Getting the infamous Unable to process the lockfile message (see attached). Have uninstalled the workstation, tried the registry hack (nothing applicable), tried the PL_AdvancedOptions_UI utility (uninstalled, reinstalled), deleted all the cdint.dll files in the system32 folder, waiting for client feedback regarding unused/obsolete printers. Nothing is working. About to involve Sage tech support. Any last thoughts before I do?


  • 2.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 08-05-2011 09:45
    - Port on the printer? - User rights for registering original Paperless (dunno if this has ever worked or just stopped cold) - Can true network admin log into system and make it work?


  • 3.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 08-05-2011 10:03
    Port on the printer is LPT1, I reregistered the CDINT300.dll, verfied that it was the correct size, right clicking on start button brought up the Explore All user so this indicates that user had local admin right. Have NOT had administrator log on for test


  • 4.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 08-05-2011 10:09
    Jeff (1) To Turn of the Paperless Office Lock File Feature: Go to File / Run / PL_AdvancedOptions_UI, and turn off the 'Use Lockfile'. Now MAS 90/200 will not use that logic anymore. (2) Client using Terminal Server? For the printer driver, make sure the ""Sage PDF Converter"" does not exist on the laptop or local workstation, but only on the Terminal Server, otherwise the local workstation's ""Sage PDF Converter"" will be redirected to the terminal server, and will get added as a redirected printer (causing errors). (3) Sounds like you tried to delete the Registry Lock folder: (1) On the Windows Start menu, click Run. (2) In the Open field, enter Regedit (3) On the Registry Editor Edit menu, click Find. (4) In the Look at area, select the Keys check box. Clear all of the others. (5) Enter PDF Converter as the search text. Search for a folder named Lock and Jobs underneath any PDF Converter keys. Typically the correct key is the Extended Solutions PDF Converter key. Delete any folder named Lock under the specified key (or keys). (6) If other folders exist inside the Lock folder, delete those inner folders before deleting the Lock folder. (The inner folders may cause the inability to delete the Lock folder.) (7) Press F3 to locate the next PDF Converter key. (8) Repeat the above steps to delete the remaining Lock folders underneath PDF Converter keys.


  • 5.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 08-05-2011 11:28
    Ken, Thanks. The file lock flag is turned off. I even turned it on, then off to see if that had any impact. Not a TS connection, just a simple XP. I would bring them up to a current SU but they have a massive radio beacon enhnancement and I shy away from SU for them now. System was working fine up to a couple weeks ago.


  • 6.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 08-08-2011 15:20
    What is interesting is that the paperless for AP invoice entry works on this workstation so it appears that the problem is isolated to SO..........


  • 7.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 08-09-2011 15:03
    Emily at Sage Tech support tracked it down to a registry issue. After cleaning it up, Client is up and running. Interesting that you can export the PDF converter registry section from a workstation that is working and import it into the ""broken"" workstations's registry.


  • 8.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 04-12-2012 10:46
    Via Citrix, getting this ""unable to process lockfile"" issue when trying to print to Paperless. But it works perfectly fine for the Administrator. I've gone thru this write-up (http://www.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=494745), but to no avail. And network rights appear to be sufficient, plus we gave the user Administrative rights - but still getting the error. Any words of wisdom out there as to why it works for the Administrator but not an individual user?


  • 9.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 04-12-2012 12:24
    After you gave the user admin rights did you re-run wksetup? I seem to remember having a similar issue - -though I do not believe Citrix was in play. The rights ultimately were the fault (as they usually are). Once we re-ran WKSETUP -- I think using ""run as administrator"" it worked. I think I may have also found that running MAS90 icon on the desktop - right clidk - run as administrator also worked.


  • 10.  RE: Client running MAS 200 SU 12 or so. XP workstatio

    Posted 04-15-2012 19:18
    Looks like we may need to install the latest 4.30 PU for 2008 server / 64-bit support.