Sage 100

MAS90 workstation setup hangs. after the crystal runtime installation finishes. I have a client that has about 35 users that log into MAS200 (version 4.4) on term server - I tried running workstation setup on the term server and it just HANGS forever. I found an article on Sage and tried the following with no success Clear these folders c:\windows\temp and c:\user\appdata\local\temp Install Crystal Reports Reboot and startup in SAFE mode Run wksetup from the CD Create a new windows user account with administrator privileges. Restart Windows and log in as the new user. also unistalled/reinstalled crystal and PC Charge client. logged in as administrator and a user with admin rights - same results. Has anyone seen this or had ideas?

Disable antivirus??

Right click - run as administrator. Usual suspect type stuff...

Never trust the administrator equivalents. Just sayin'

I did right click and run as administrator - the anti-virus is password prot,ected and I wanted to try that as soon as their IT company opens ths morning

I guess I have not tried running as administrator while logged in as administrator - I'll give that a shot

Are you sure it's hanging (possibly a dumb question). I find that it takes a while after the Crystal runtime starts for it to finish.

it was definetly hanging (I let it run for over 2 hours) it gets past the crystal install then copies more files and never gives me the finish screen (just sits on the installing screen with the progress bar all the way at the end. I think I have it working though. I looked at the SOTA.INI file on the 200 client and there was no server information - I manually typed that in and it launched. I'm not sure if I will have any other problems but with 35 users about to log in over the next hour I'm sure to find out quickly. :) Thanks for the quick replies.

Looks like I MIGHT be out of the woods. although it is Friday the 13th. Note to self - double check the ""Path="" portion of the SOTA.INI - don't assume you spelled it correctly :) Again - thanks Wayne and Scott for being there so early in the morning!

Try stopping the Windows print server service if it is a Windows 2008 server.

I had this same issue and it was resolved by stopping the print spoiler service. Try that!

Spoiler or spooler???

Spoilers!

Had this same problem on a Windows 2008 server and stopping the print server service took care of it.

Stupid auto-correct. SPOOLER!! Although most printers are spoilers...

I checked and there is a print spooler running on that machine - I will remember this for future reference. We still can't get the paperless office working on this machine - I spent an hour with a Sage tech Friday and we did not get it working but there were several Sage PDF converter (redirected ) showing up as printers that I could not delete even logged in as Admin. So the IT staff is going to work on getting rid of those today

Is it all running on the one machine or is the MAS Server on a different machine than the terminal server. When defining the jobs you must consider the path from the client and not the server.

Yes it is on a different server. When you say defining the jobs are you referring to the form setup in paperless? we have that set to a UNC path and I did just verify that the UNC path is accessible from the term server and all users do have rights to that folder

Just had this exact issue - didn't find anything on Sage KB about print spooler/spoiler:), but thank goodness for 90 minds - stopped the printer service and immediate sucess!

I love this forum, just fought with workstation setup for about 1-2 hours and finally came out here and found this same problem. Turning off the Print Spooler solved the problem. Thanks everyone!