All Answers
The odd part about this is that it is just one computer that is showing the problem.
The server had been rebooted yesterday, which may be related. The one user was successful with remotely running QB on Wednesday but not on Thursday after the server reboot. It is likely that there were Windows updates that installed on the server as part of the reboot.
The workstation should be current on Windows updates. According to the user, the last update was before the last time he successfully ran QB.
I looked at note 3 in your first link. The server was set to keep QB running. I’ve since disabled that.
I looked at your second link. Though we’re not getting that message, I checked the settings. IE Enhanced Security Configuration was already off. The Internet zone Security settings are set to Custom. I don’t know what was changed in there. I’ve done a backup of them from the registry but will put off resetting them until further testing.
I’m skeptical about this being an issue on the server as it works for other workstations, both remote and local.
- RS answered 9 years ago
I got my hands on the laptop yesterday and it has gotten more “interesting”.
I found that there was a hardware problem with the hard drive, so I put in a new one and started from scratch. I installed Windows 10 and copied over some data from the old drive. I copied an RDP file that works fine on my computer, but the problem persists!
I created a different user on the workstation, on the server, and in QuickBooks. It shows the same problem.
I can successfully run QB remotely from a variety of other computers using the same credentials (both for the remote connection and for QB), just not this one laptop. I ran a Windows Memory Diagnostic and it reported no errors.
What could be going on in the workstation that affects the remote application?
- RS answered 9 years ago
Oddly enough, the issue resolved itself!
What may have made the difference was logging into the server directly with the user’s credentials, starting QB with his credentials, then logging out of both.
It still makes no sense to me why the symptoms were different when the same credentials were used on any computer except the “problem” one, but at least it’s resolved now!
- RS answered 9 years ago
Thank you for your input on this issue. Feel free to delete this thread if it seems appropriate.
- RS answered 9 years ago
I spoke too quickly.
The error would occur before the QB desktop occurred originally. Once I saw that this was working, I assumed it was fixed. The same error comes up now when you try to create a new invoice.
As before, I can log into the server as the same user, log into QB as that user, and it works without error.
I can connect with WSE through a different computer, same user as the problem one, and it works fine.
What could there be in the computer that affects QB running on the server?
- RS answered 9 years ago
RemoteFX will not work on an Essentials server (nor with WSE RemoteApp) because it requires that the Remote Desktop Session Host (RDSH) server role be installed, and that server role is not compatible with Windows Server Essentials (nor with WSE RemoteApp). RDSH wreaks havoc on the default configuration of the Essentials server, and WSE RemoteApp will actually refuse to run if the RDSH server role has been installed on the server (since it is designed to run with the server in its default “Remote Administration” mode, and RDSH places the server into “Application Server” mode instead).
- Mike answered 9 years ago
I have a HyperV server which is running WSERemoteApp as aVirtual Machine.
The RDSH is running on the HyperV Server so it would mean I would be adding the RemoteFX adaptor to the Virtual Machine itself, so the role wouldn’t be affecting the WSERemoteApp Virtual Machine.
Is this going to be the same if I add the RemoteFX adaptor to the WSE Virtual machine?
- scott answered 9 years ago
Installing the latest version of the program (which is currently Version 1.255.1293.0/1.1255.1294.0) should resolve that issue for you.
- Mike answered 9 years ago
I hope i understand it right.
The Problem is, that the program Version is to old?
So i have to pay again, that i can use it?
- Maik answered 9 years ago
- last active 9 years ago
I haven’t come across that particular error before, but changes have been made in this area in the latest releases of the add-in (and so installing the latest release may resolve the issue for you). For the most part, older versions of our add-ins will continue to run for a long time (many years), but on rare occasions, backend security changes made by us (or Microsoft, etc.) can cause an older version of an add-in to stop running. In such cases, you will need to install the latest version in order to continue using the software. For more information, please see the “Updates and Support” section of our Policy page.
- Mike answered 9 years ago
Alas, I’m afraid not. To the best of my knowledge, there is no way to run RemoteApp programs from a Chromebook. I’m not very familiar with Chromebooks, but in order to make it work, the Chromebook would require an app (such as Microsoft’s Remote Desktop app for Android) installed on it that allows it to act as a RemoteApp and Desktop Connections (RADC) client for consuming the add-in’s RADC web feed. However, I don’t believe that Chromebooks support installing apps at this time.
- Mike answered 9 years ago
I am also having the same problem with RADC. We have an app we would like to access remotely, but when adding the url to remote app access on Windows 7, it says the URL is invalid. Looking up the error code (event 1004, 0x80040204, 0x0) confirms that the issue is with the URL, but I have checked and it is correct. This is Windows 2016 essentials experience. The Maven rw and all other remote web access functions correctly with a valid GoDaddy cert and it shows up in IIS for the default web properly . I decided to purchase the product because I wanted to use the RADS and could not test without a purchase. I dug a little into the IIS folder for RADC and see that two RDC sessions saved to deploy open and try to use a self-signed cert. Since Remote Desktop Gateway Manager is not available on this machine (hence the purchase of the Maven product) I cannot modify the RD Gateway settings to use a different cert. I see no way to modify these. Is this the reason for error? The product is clunky for our usage without this functionality (RADC).
- NAtalie answered 9 years ago
- last active 9 years ago
Hi Natalie,
I believe that I already answered this one for you via email, but I’ll go ahead and post it here as well because I believe that it may help out others who are using Windows 7 client computers and can’t get WSE RemoteApp’s RADC web feeds feature working (i.e. they receive a “The URL you typed does not have a connection.” error when attempting to set up the web feed within the Windows 7 RADC client in the Control Panel).
Okay, I think I’ve figured it out now…
The update that is breaking WSE RemoteApp’s RADC web feeds feature in Windows 7 is this one:
KB2830447 – Update for RemoteApp and Desktop Connections feature is available for Windows
It’s an “optional” Windows Update that doesn’t get installed during a normal check for Windows Updates (which is why I didn’t notice it before). And, once it gets installed, WSE RemoteApp’s RADC web feed feature stops working.
That being said, the reason that WSE RemoteApp’s RADC web feeds feature stops working when you install KB2830447 is because it has a prerequisite Windows Update that doesn’t get installed along with it (when it probably should! – Silly Microsoft, Trix are for kids!). That prerequisite Windows Update is:
KB2574819 – An update is available that adds support for DTLS in Windows 7 SP1 and Windows Server 2008 R2 SP1
Apparently one of the improvements Microsoft made to the RADC client in Windows 7 (with KB2830447) made it so that the RADC connections now require DTLS (for increased security – like in Windows 10).
So, if you go ahead and install the “optional” KB2574819 onto your Windows 7 client, WSE RemoteApp’s RADC web feeds feature “should” start working for you once again.
That took some crazy sleuthing on my part to figure out, but I think that I finally licked it! Please do let me know how it goes.
Oh, and BTW, you can also go ahead and re-install the August 8, 2017 Monthly Rollup (KB4034664) Windows Update on your Windows 7 client again, seeing as that wasn’t the culprit after all. Mea culpa!
- Mike answered 9 years ago
Since WSE RemoteApp is not showing up on the Dashboard’s “APPLICATIONS” page, you can try this in order to manually uninstall it:
1. Make sure that the server Dashboard is closed, and that any/all user WSE RemoteApp sessions are signed out. It will also be helpful if all of your client computers are online and connected to your network (and their Launchpad application is signed in and connected to the server).
2. Start a standard Remote Desktop connection to your server and sign in as any user with admin rights.
3. From the admin user’s desktop, open/run the Registry Editor (Regedit.exe) and go to the following registry key branch:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{2B1AA239-CBA4-41AB-A281-35A7C69B104A}
4. Locate the “NoRemove” value and change its value data from 1 to 0.
5. From the admin user’s desktop, open/run the Control Panel’s “Program and Features” applet.
6. Locate the “WSE RemoteApp … Server Add-in Deployment” program in the list of installed programs, and uninstall it.
That should do it. WSE RemoteApp should now be completely removed from your server (and all of the client computers that were online and connected to your network).
- Mike answered 9 years ago
I’m afraid not. WHS RemoteApp 2011 requires the “Essentials” components of Windows Small Business Server 2011 Essentials in order to function. Therefore, it will not work with Windows Small Business Server 2011 Standard.
- Mike answered 9 years ago
- last active 9 years ago
As per the Higher Editions section of our Policy page, you can move up to a higher edition of our products by simply paying the difference in price between what you paid for the lower edition of the product, and the current retail price of the higher edition that you wish to move up to. So in your particular case, you can move from the 15-user “Business Edition” of WSE RemoteApp 2016 up to the 25-user “Professional Edition” for only $75 USD (i.e. the current difference in price between the two editions).
If that is agreeable with you, then contact us for a direct PayPal payment link that you can use to submit your $75 USD payment. Once your payment has been received, you will be sent an email message containing your personalized registration information (with the exact same User Name, but a brand new Registration Code) for use with WSE RemoteApp 2016 (Professional Edition). You can then use that new registration information to re-register the product, and it will automatically be moved up to the higher edition. There is no need for you to uninstall/reinstall the add-in, and all of your published RemoteApp programs, settings, etc. will remain intact during the registration process.
- Mike answered 9 years ago
- last active 9 years ago
You can automatically move your license to a different server once every 21 days. When you install the product on the new server, it will alert you that your license is currently in use on a different server, and it will ask if you want to move the license over to the new server instead. If it has been less than 21 days since you last moved the license, then it will not give you the option to automatically move it, and you will need to contact us in order to manually move the license over for you. Thus, you should not have any issues with purchasing the product, running it on a test server, and then moving its license over to a different production server once your testing phase has completed.
- Mike answered 9 years ago
- last active 9 years ago
Anywhere Access / Remote Web Access is not a feature of my software, but rather a built-in feature of the Windows Server Essentials operating system (that is used by my software). For help with configuring Anywhere Access / Remote Web Access on your Essentials server, please see the following Microsoft documentation:
Manage Remote Web Access in Windows Server Essentials
Troubleshoot Remote Web Access connectivity in Windows Server Essentials
- Mike answered 9 years ago
Microsoft recently released a Windows Update for Windows Server 2016 (KB4038801) that broke WSE RemoteApp 2016‘s multiple simultaneous connections feature. The problem has since been resolved in the latest release of WSE RemoteApp 2016 (i.e. Version 1.255.1303.0 or greater). Thus, installing the latest version of WSE RemoteApp 2016, and then running the “Enable simultaneous connections” task again from the “WSE REMOTEAPP” page of the server Dashboard will resolve the issue for you (note that a server restart is required).
And yes, this was exactly the reason for the recently released update of WSE RemoteApp 2016.
Unfortunately, a history/change log for WSE RemoteApp is not available. I’ve been meaning to start one, but just simply haven’t got to doing so yet. Mea culpa!
- Mike answered 9 years ago
- last active 9 years ago
The latest Windows Updates that affected WSE RemoteApp 2012 R2‘s multiple simultaneous connections feature are KB4034681 (first published 08/08/2017) and KB4025336 (first published 07/11/2017). In both cases, WSE RemoteApp 2012 R2 was immediately updated to resolve the issue. Thus, installing the latest release of WSE RemoteApp 2012 R2 (i.e. Version 1.255.1294.0 or greater) on a fully up-to-date Windows Server 2012 R2 Essentials server, and then running the add-in’s “Enable simultaneous connections” task again from the “WSE REMOTEAPP” page of the server Dashboard should resolve the issue for you. If not, then please contact us for additional support.
Lastly, in order for WSE RemoteApp to have a fully functional uninstaller (just as you’d expect it to), uninstalling the add-in will indeed completely remove all traces of the add-in from your server and client computers (including all of your published RemoteApp programs, custom RemoteApp program properties, settings, etc.). Therefore, it is not recommended that you uninstall the add-in unless you absolutely need to (or are directed to by support, etc.). Otherwise, you will need to completely set up the add-in from scratch again (just as you’ve found).
- Mike answered 9 years ago
- last active 9 years ago
