Sage 100

 View Only
Expand all | Collapse all

Sage 100 Standard 4.50. New employee added. When

Phil McIntosh

Phil McIntosh03-10-2015 10:04

Phil McIntosh

Phil McIntosh03-12-2015 15:25

Steve Iwanowski

Steve Iwanowski03-12-2015 15:29

  • 1.  Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 08:56
    Sage 100 Standard 4.50. New employee added. Whenever her MAS user is logged in, the entire system slows noticeably. Printing takes twice as long, for everyone. They have already deleted the MAS user and created a new one - same issue. It is not tied to a windows login or workstation. Any ideas?


  • 2.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 09:00
    I'll be watching this one - have a client where certain users (newer) lock up or get connection errors. Sage blaming it on UDFs. Not.


  • 3.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 09:11
    @BethBowers - has your customer been on MAS a long time? Ours goes back to 3.xx days. Wondering if the accumulated years of users might have something to do with it.


  • 4.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 09:21
    I've had similar issues which turned out to be physical problems. One ended up being bad (and over-long) network cabling. The other was a bad network card, but you're saying that the trouble follows the MAS user from PC to PC?


  • 5.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 09:42
    @SteveIwanowski - mine definitely follows users. And a different user on the original workstation does NOT have issues.


  • 6.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 09:44
    Anything to do with User Longon length or short user code length? Back in the v3.xx days short logon codes played periodic havoc.


  • 7.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 09:50
    Did you delete the SY_Workstation - have you ran a windows update on that pc and completely patch and looked to see if there were any NIC patches?


  • 8.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 10:04
    Check Spawn Tasks and ODBC setting in that User's Preferences; and compare to other users. Most likely, they are running as a Service, and never made the registry hack. I would guess the other users are ""spawning tasks"" and this user is not. I recommend rebooting the server at some point, after you get this fixed to clear up any orphaned tasks.


  • 9.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 10:04
    It definitely follows the MAS user.


  • 10.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 10:05
    Server has been rebooted - this is MAS90, not 200.


  • 11.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 10:34
    Grasping at straws: Is there a specific printer tied to that user that would follow them? Are there other users that have the same roles? Do they have any potentially reserved words in their user code/name like CON or DEF?


  • 12.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-10-2015 11:18
    Printers are networked. Others in same role. User code is SKS, name = Sophea.


  • 13.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-11-2015 07:20
    You might DFDM the user file and just look at that user's record for any odd settings.


  • 14.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-11-2015 11:07
    if going down the printer hole - Delete any printers that are offline and not used anymore - check the server also. I would check other users also.


  • 15.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-12-2015 15:25
      |   view attached
    And now this, while logged into their server


  • 16.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-12-2015 15:26
    Yikes. Nuke it from orbit, it's the only way to be sure....


  • 17.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-12-2015 15:29
      |   view attached
    I think I am going to start all troubleshooting of odd behavior by searching for ""*crypt*""...


  • 18.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-12-2015 15:29
    I would start with a CHKDSK on the server. Then copy the MAS90 folder back to your own system to see if it follows the files. Then maybe copy the company to a virgin install.


  • 19.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-12-2015 15:29
    Ugh, time to test that restore process...


  • 20.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-12-2015 15:31
    And I am definitely NOT going to copy the folder back over to my machine...


  • 21.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-12-2015 15:33
    Send it over to @SteveIwanowski - he'll test it on his server


  • 22.  RE: Sage 100 Standard 4.50. New employee added. When

    Posted 03-13-2015 05:16
    C'mon everyone, where's your sense of adventure! Actually, with CryptoWall/Locker, the data files are harmless.