Sage 100

I have a 4.40 M200 client getting Windx client connect error 15. Already set sota.ini file to use IP address from client, but it could be wrong. Any other suggestions?

Have you tried a different port number? The port number and not enough security has given me similar errors recently.

They were fine last Fri, so something changed over the weekend.

Couple of questions. Were they a recent upgrade? How many users? On the server are they running as a Service or Application?

running as an app, not sure of user count. upgraded a few months ago

What about the Antivirus software - recent updates or changes in antivirus software way cause a problem.

verified IP address correct. i'm launching MAS on the server w/ this error. I stopped McAffee services.

On the server have you tried getting everyone out, stopping the application and then renaming the Home/Lib/_appserve/locate.pvk and sessions.pvk files and then restarting the application?

yes, but not since changing from the server name to the IP address in the client sota.ini file. I can do it again.

same error

Just out of curiosity, can you run MAS 200 in MAS90 mode on either the server or workstation?

Are you getting the error from all workstations or just the one? Maybe have your user try from another workstation. Log onto workstation as an admin and try from the problem workstation.

getting the same error on all wkstns. Haven't tried running in MAS90 mode yet.

Sounds like we need Alnoor on this one.

Dang it BL, you beat my post regarding Alnoor.................

It works better when you say ""Sounds like we need @AlnoorCassim on this one"".

Dang it Robert, you beat my re-post regarding @AlnoorCassim

What is the # of users going into MAS200? We've had these issues when approaching the 20ish user mark. We had one we went to 4.4 on that had very similar errors. I think this is a summary of some of the MAS200 server debug tactics http://www.s-consult.com/2008/10/08/tips-how-to-set-up-an-application-server-in-sage-mas-200-version-4x/

OH and the cure in my case was to run the MAS200 as an application and not service.

It's running as an application-There's a checkbox in the configuration Use CmdAsUser, that got selected, possibly by the user. And the IP address WAS incorrect, even though they thought it was right. So fixed the IP, unchecked the box, the error was resolved. Thanks Everyone!

First rule of debugging is ignore the IT department when they tell you that it couldn't possibly be someone as simple as what you suggest... ;-)

It usually is ""someone"" that simple...:-)

Sounds like someone has some 'splaining to do. How did the IP address get changed from correct to incorrect?

Sorry @RobertWood and @LouisAraiza forgot to change back SocialCast notification settings since coming back from Disney Cruise. @CindyIsche - Glad it's resolved! General note - whether it's server or IP, there are 2 places on client side to change: 1) In Sota.ini AND on the MAS 200 shortcut target. If you fix it on 1 but not the other, error persists. Also on my own last Error 15 on MAS 200 startup, I did this: In location where Wkstn Setup was run, open that pvxwin32.exe and type this: open(1)""[tcp]192.168.1.70;9500"" Substitute that IP and port with the real one. I got an error 15 this way too (meaning external cause) and led me to discover some internet security software was blocking my request. But had it returned me to a -> prompt on the next line (that is no errors), it means that IP and port are good, ergo look in Sota.ini and in shortcut target path for discrepancies. Hope that helps for future. Good catch on the CmdAsUser !

Post a picture of you with Mickey at a Character breakfast.......................