Sage 100

Hey everyone. I have a persistent issue on a client terminal server that the client can't seem to resolve. Every non-Sage 100 user who tries to open an RDP session on the server gets a message that the Sage 100 version 2014 client is trying to load but the files can't be found. I have attached screen shots. Sage 100 Standard version 2014. Here is the exact message I am getting from my end user: 'When a non-Sage 100 user logs into the terminal servers and launches a non-related application, they get the following message: They have to click OK, then Cancel several times before they are able to proceed with their work. Active users of Sage 100 do not get this message and are able to use Sage just fine."" Thanks in advance for any help you can offer.

A couple of questions 1. What the heck is Prime Suite and could this be interfering? 2.Can we aqssume that the installer is not hung on the server causing this problem? Have you rebooted the terminal server, or are you afraid to because users are in and working 3. DO you have an alternate RDP server or a local client you can launch for testing purposes?

Have you disabled and/or uninstalled the Sage Advisor?

@GaryFeldman, Prime Suite is another program the end user is attempting to load that has no connection to Sage 100. Any non-Sage 100 user that logs onto any RDP server with the Sage 100 client installed immediately try's to install the Sage 100 client. It doesn't matter that the user had no rights to the program and didn't try to launch it. The installer is not hung. The RDP servers (4 in all) have been rebooted multiple times. If a Sage 100 user logs on, the app doesn't try to launch, probably because it is already installed under their profile. @MichellePage, Sage Advisor is our next option. I will have him remove it from one of the RDP servers and see what happens. Can't get worse can it? (Never mind, that was my silly inside voice getting out. Of course it could get worse!)

WAG... persistent mapping is disabled.

I'm having a similar problem with a client that runs an Access database at three locations. The Access database uses the ODBC connection to read data in the Customer file. Both Sage Advisor and PEP is not running on the terminal server. @MarkKotyla Where do I find the persistent mapping option?

It's usually part of a user or system login script. http://loginscripts.com/network-drives.asp

Shawn - I'm not sure what's kicking off your workstation installation. I did find that we dealt with that specific error 2 different times. In our case, it popped up in the middle of the workstation installs. This is what Sage gave us back then. ""Error 1706 No valid source could be found for products"" when installing Workstation Setup Entry Type: Informational Product: Sage MAS 90 ERP, Sage MAS 200 ERP Application: Library Master Version Reported: 4.10 Subject: ""Error 1706 No valid source could be found for products"" occurs when installing Workstation Setup for Sage MAS 90 or 200. Possible Resolution: Note: Sage Software, Inc cannot assist in this task contact a computer technician. This is a Microsoft Windows error indicating that a Windows component may be damaged on the workstation. The Windows installer may be damaged on the workstation's operating system. To resolve, use a Windows installation cleaner utility or reinstall the operating system. Related Link: Error 1706 ""No valid source could be found"" when installing MSI file from removable media Note: Sage Software cannot guarantee nor be responsible for the content of third party Internet sites. Contact that site's Webmaster with questions or problems.

Hey @ShawnSlavin have you made any progress on this issue. At my client the issue has escalated because now all three remote locations are experiencing this problem. I looked in Event Viewer on the terminal server and pulled 14 screen shots that show the sequence of ""events"" that are captured by terminal server Event Viewer. The attached PDF shows what is happening starting with the first event triggered by an Access program tying to print to a PDFCreator printer. The first event @ 2:19:59pm -Warning....detection of product ......feature 'Sage_Intelligence_Reporting', component ........failed'. The resource 'C;\Program Files\Sage\Sage 100 Standard ERP Workstation\MAS90\' does not exist. This first event is followed by 13 subsequent events. The only way to stop this is when they are able to terminate the Windows Installer event @ 2:20:44pm using task manager. This client does not use Sage Intelligence, but did recently upgrade from version 4.4 to v2014. What do I need to do at the three remote locations to make this problem go away?

@KatrinaEddins - I do not remember hearing about this particular error message in our facilities. Can you search our service module and see?

Micheal, Have you looked into the BI Tools for SIR installing/or trying to install in those RDP sessions? Can they login as the administrator to complete the install, then disable the BI Tools in Excel? Also, do the users have full control of the MAS90 folder - seems like the message says that the process can't write, maybe the MAS90 folder or the registry itself?

@MichellePage you might be onto something. I have used GoToAssist or LogMeIn and remotely connect to their workstation. I then have them RDP with their login ID to the main office terminal server. They normally do not run SAGE 100 ERP Standard, but I launched it and was able to get into SAGE 100 ERP Standard v2014 with no issues. Then I had them launch their Access program (not Excel) and they are able to print to the PDFCreater printer without issue. I will ask their IT folks if the remote users have rights into the C:\Program Files\Sage\SAGE 100 ERP Workstation folder on the terminal server. But what is SIR trying to launch anything? The client have never installed or used SIR in the past?

When the 2014 Workstation/Client is installed, there is an Excel piece that installs automatically for SIR. If the users don't have rights to run the install, this could be causing the problem. Yet, in the screenshots (more vaguely) we can't tell where the program is trying to install. I have learned that in newer Windows OS, users do not have edit rights by default in the Registry - I believe it is HKEY_USERS. Therefore, if the users don't have rights to either the folder where the program is trying to 'update' or the registry, it could cause this loop. I have also seen Crystal conflicts cause this look with Windows Installer.

How can you tell if a remote user has edit rights in the Registry of the terminal server?

When they login, go to Start > regedit, then on the HKEY_USERS node right click, then click on Permissions. You will see the Security tab, showing the current users' permissions (select the appropriate role in the list).

@MichellePage I just determined that the problem I'm having is NOT a permissions issue. I was able to duplicate the problem with my terminal server login and I have Admin rights! The problem keeps pointing to SIR - I discovered that a BI Generator was installed into the Microsoft Office Suite on the terminal Server. This showed up in Excel 2010 and is shown as a COM add-in. Disabling the BI Generator - COM Add-in did not solve the problem. Can SAGE Intelligence (SIR) be installed on a terminal server? Do you think if I install SAGE Intelligence from the SAGE 100 ERP Standard Workstation menu will make this issue go away? Thanks for all your help!

@MichaelMcDonald Yes, SIR can be installed on a Terminal Server, yet it is only compatible with 32-bit Excel for Sage 100 v.2013 and lower. In addition to disabling, can you uninstall the add-in?

@GaryFeldman no we haven't seen this error in our cloud environment.

Well I've uninstalled the SAGE 100 ERP Standard v2014 Workstation client from the client's terminal server and the Access program is now working again. When I was performing the uninstall I received a pop up box ""Microsoft Office Customization Installer"" The error was pointing at C:/Program Files/Common Files//BIGenerator/AlchemexWizard.vsto. Is there a way to install the SAGE 100 ERP Standard v2014 Workstation client and NOT install the Sage_Intelligence_Reporter components?

@MichaelMcDonald, @ShawnSlavin, do you recall how this one ended up? Did you end up getting it to function properly?

Brett, the client had enough users on a terminal server farm that they dedicated a server for the Sage 100 users. Now the other users don't see it as the app isn't loaded on the server. Sorry @MichaelMcDonald for not getting back sooner but I had to connect with my guy at the client shop to get an answer.

@BrettZimmerman No, I have not been able to determine why this is happening. I'm currently searching for the answer. This problem has occurred at a second client location, just last month. They have two Windows 2008 terminal servers to balance the load of remote users. The majority of users on both terminal servers access an SQL database and do NOT access SAGE 100. The SQL users are getting the following install messages (The errors are shown in the order they appear) when they launch SQL system. The smaller number of users that access SAGE 100 on both terminal servers do not have issues. @ShawnSlavin I guess I could advise the client to split up the users and put all non-SAGE users on one terminal server and all SAGE users on the second, but that might negate the ""load balancing"" feature of having two terminal servers.

@MichaelMcDonald Have you tried to uninstall Sage Advisor? Also, although I'm not aware of a way to stop the install of the ""Microsoft Office Customization Installer"" during the workstation installation, you can disable the add-in in Excel. Not sure why that add-in would be impacting Access.

@MichelleTaylor Yes, Sage Advisor has been uninstalled on both terminal servers. The SI Excel Add-ins have been removed, but we still get the Workstation installation startup for all non-Sage / SQL users on both terminal servers.

@ShawnSlavin , is this resolved? You mentioned term server farm. I've had to install the client on every one of the term servers (of course, but in my case involving IT because I didn't know how to PICK which one I connected to). You probably already covered that weeks ago, but just in case!

@RhondaMcNamara Unfortunately no. They had a large enough farm that they put the accounting folks on their own Terminal Server and put everyone else on a separate farm.

And looking at the KB, which Mary Jo posted already, I guess you already ruled out permissions by logging in with god like rights. And the other obvious...seeing if you can see that path by putting it in the run prompt box. Did you look at DEP? Sometimes that does weird things. (Right click My Computer / Properties / Advanced System Settings / Performance / Settings / DEP the top radio button is the one you want. And last resort... did you install the proper method for a term server, which in the old days was through add and remove programs, which I understand is the T/S equivalent of putting it in Install Mode.

@RhondaMcNamara we finally worked around it. We didn't have the time or desire the fight every possible avenue. Regarding the security issue, we sure weren't going to give every user who might log on any particular server in the farm 'God Like' security rights.