Sage 100

Client on MAS90 v4.5, after Windows update 99% of users are unable to launch tasks. Window appears minimized, cannot do anything but close. Only me (using Windows 8 accessing via RDP thru Server 2008) and one other user (who restored then reinstalled update) works properly. IT guy swears it is MAS90 only. I cannot convince this guy MAS is not smart enough to perform such things. Any ideas? I am totally lost.......

Internet Explorer 10 would be my first hunch. See if that can be removed.

Is the one user not having the issue a local administrator on their computer and the others are not? I have had issues on terminal servers where those without administrative rights had MAS tasks open as minimized icons on the task bar. They could open they by click on the icon on the task bar. This differs from your case, but could be a rights issue.

Most likely IE 10.

Maybe the information in this thread will help? https://90minds-com.socialcast.com/messages/14440010

manually open the path MAS90 opens in the address bar in IE and click on the IE compatibility for that site. then try opening mas90. Also make sure you are starting MAS90 as windows Admin rights.

This is going to sound odd but I have seen the same thing happen on my notebook. For some reason, my machine some times thiinks it has a second monitor attached to the left of my primary display. Other times, an app just opens 'off screen'. I run windows 7. If I hover over the app on the start bar (in my case at the bottom or my screen), a second window or button will pop up. I right click on that, choose move, click and drag my mouse a little and then use the arrow keys. If going right for a little while doesn't work, try left then up, then down. It is possible the form is open off the screen. I can't explain why it happens, just give it a try. If this doesn't work, try two martini's in quick fashion then try again. I find enough martini's makes anything less irritating! Cheers!

@Brett - the thread you mentioned does not apply here, but thanks. The task requested never actually launches, only the ""MAS90 is not responding"" message appears, but minimized so small you cannot read it. The window does not give any option but Close, all others are greyed out. I will try @Shawn's suggestion. Funny thing, some users are able to work for a while, then this crud starts happening again. I can work just fine through RDP on Windows 8, the VP Finance has not had any issues either. She initially had problems with her workstation in general after the Win7 update. They completely unwound the update, then manually installed it. She is working just fine and has been all along - now the Sales Dept. is working fine as well. We did nothing to them..........The IT guy got belligerent when I said it cannot be the MAS90 program, but it could be the Server.

OK - now I am REALLY CONCERNED. Now I am getting the ""MAS90 is not responding"" message. Although I can see the little guy a wee bit better than everyone else, it still comes up minimized and the window is blank. The only reason I know what it says is due to the Task bar giving me the hint :( ""I love my job, I love my job, I love my job"".......

What antivirus are they using? I have seen AV updates, particularly from VIPRE, cripple MAS 90.

How about User Account Control (UAC) did the Windows Update turn it back on. On Windows 7 and 8 machines it should be turned off.

OK here's the latest........the MAS Server is not releasing the PVXWIN32.exe when users close a task or when they close the program. What is up with that? Why would a Windows update cause something like that? I just checked the Server; over 100 instances of PVXWIN32 running - including 6 users who have logged off and left for the day! OH......not all users are Windows7 - I have two still on XP. Just thought I would throw that in :)

Those stranded pvxwin32 instances may be a symptom, and not the cause. If the communication is breaking, the server processes never get the ""close"" message.

I'm with Phil, check the AV definitions and exclusions on the MAS server itself, and (if possible) reboot the server. As a workaround, you may be able to use MAS 90 mode on the PCs. http://infosource.sagesoftwareonline.com/infasp/kdb.asp?isresolutionconceptid=405250

@SteveIwanowski how did you get the infosource link??

The ""old"" knowledgebase is still working (for now...). http://infosource.sagesoftwareonline.com/infasp/search.asp

OMG! I just tried yesterday and while I got results, I wasn't able to open any!!

@SteveIwanowski, interesting! The ""old KB"" link I have (and apparently lots of other folks) is: http://infosource.sagesoftwareonline.com/sw_attach/search.asp - whereas yours is http://infosource.sagesoftwareonline.com/infasp/search.asp Notice the /sw_attach/ vs. /infasp/ . So I guess technically the ""old KB"" is in fact working assuming you use the latter link. Thanks, Steve!

Nice catch @BrettZimmerman

Notice how we all get excited about the old KB?? Kind of a sad statement.

The sad part is that so little has changed you can reasonably well use that old static KB...

It is also nice for sharing links with customers who don't want to login to the Sage disaster site.

Wow Thanks @BrettZimmerman thought it was only me that couldn't get anything to print.

I think the thanks go to @SteveIwanowski AND @BrettZimmerman !!

You are right @ThereseLogeais Thank you @SteveIwanowski! I just got so excited that I could print from the old KB LOL..

@KathleenMatthews - your thread has been hijacked in celebration of that rare instance when software actually works:-)

Can we get back to my problem please? My client is dead in the water. I don't mean to be selfish, but I REALLY need help here..... We have rebooted the Server numerous times, only to have the tasks start spawning all over again.

Assuming you already kicked everyone out, stopped the MAS service, killed the orphaned PIDs and restarted the service, what else have you tried? Did MAS 90 Mode work? Was AV configured correctly? Is UAC on/off on the server/clients? Does MAS work fine on the server itself (in either 90 or 200 mode)?

Sorry, missed the part that said you already rebooted, but please let us know about the other questions.

Have you tried having one of the workstations with the problem do a system restore to before the windows updates?

I'm connected right now with Kathleen on the 2003 Server. Looks like it's the Kerberos Ticketing issue. Does anyone have handy the actual location(s) in the registry to edit the values? I know @JeffSchwenk you posted the screenshots once too.

I found this older post. May not be what you're looking for, however. https://90minds-com.socialcast.com/messages/6574506

I can't find the reg-key, but the Group Policy is here: Computer Configuration\Windows Settings\Security Settings\Account Policies\Kerberos Policy\ http://windowsitpro.com/site-files/windowsitpro.com/files/archive/windowsitpro.com/content/content/15313/userticket.gif

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters\TgtRenewalTime

Even as domain adminstrator, we are in read only mode when using GP Editor for some reason

Is it an SBS 2003 server, or just a 2003 member server? You may need to edit the Default Domain Policy on a domain controller if it's the latter. Wasn't the workaround for that Kerberos Ticket issue to just reboot the PC?

Not an SBS Server, just a Member Server. Why would be in Read only?

If it's a server in a domain, then the domain controller dictates the group policy settings. Usually GPEdit doesn't show as read-only (the IT guy could have locked you out), but any changes that are made to the member server that conflict with a policy will be overwritten back once the member server reboots. Switching gears, can you browse to any of the shared folders on the MAS server from a PC?

@SteveIwanowski - this is a MAS90 installation, not MAS200. No service to stop, no MAS90 mode to try.... Yes, I can browse to the MAS-XXX folder, as can all users. But .....I just tried to run a VI job and got an Unlock Region Failure message. (I am going through Terminal Server 2008). I checked the TS and saw a few other users locked up - one with a MAS task of 14k KB, BUT he has inquiry rights only. How can he spawn a task that freakin' large (screenshots attached)?? One other question....might be a dumb one....should UAC be turned off on the TS as well as the workstations?

So all the users are running it on this terminal server? Have you tried turning off the AV? UAC?

No, all users are not running on Terminal Server. WMS scanners, me and some of their OS salespersons. Everyone else goes directly to the FILESERVER. However, I do notice when a TS user has a stuck session at 14k KB or the like, we start getting ""MAS90 is not responding"" messages and Unlock Region Failures. UAC is turned on at the Terminal Server, Symantic End Point AV runs, IT guy has that locked down tight. I have sent no less than half dozen Email with exclusion instructions.....Exclusion tab not highlighted. But he thinks his ""you know what"" smells like roses, and I am ""just a MAS90 consultant""...so I must tread lightly.