RemoteAPP crashes from just one computer

I have a very odd situation for which I'm looking for assistance.

I have a client with a server running Server 2012 R2 Essentials.  They use WSE RemoteApp to allow remote users to access QuickBooks Enterprise 16.  This works fine for several users, except for one who just recently started having problems.  He can connect to the server and log into QuickBooks, but QB will abort moments later with an Unrecoverable Error.  The Code is 19758  66888.  I'm not finding anything online about that error.

What is particularly odd about this is that it only occurs with this one computer.  I try the same thing on another computer running the same version 1703 (and build) of Windows 10 Home, from the same location (have tried 2 different locations), using the same login and QuickBooks credentials with no problems.

I have installed a new hard drive in the laptop and reinstalled Windows 10 from scratch and the same symptom occurs.  The BIOS and drivers are up to date with no errors.

When I reinstalled Windows, I did copy user data (Documents, etc.) from the old drive.  I thought that might somehow be the issue, so I created a new user on the computer.  It shows the same error.  Both users are local admins.

The only common element with the failures is this specific computer.  The error is coming from QuickBooks.  I'm not seeing how something in this computer can cause the application error in the host computer.

I added a new Windows user on the server as well as a new QB user but still get the same symptoms.

I ran Windows Memory Diagnostic with no errors detected.

I've communicated with the company that produces WSE RemoteApp, but didn't get any solid answers there.

Any thoughts on what to look at next would be appreciated.
LVL 23
CompProbSolvAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
Based on the description of the WSE product, the application is still running on the server. Is it possible to log on to the server directly/remotely and run the program there for any user? Basically trying to get this RemoteApp thing out of the picture, because I'll bet if you called Quicken they'll say it is not supported running in this way.

You have done a pretty detailed troubleshooting job already. What about disabling antivirus?

It could be something weird about the particular system, unless that second computer you tried is the same hardware.
0
CompProbSolvAuthor Commented:
WSE used Remote Desktop and adds the RemoteAPP feature that isn't present in Server Essentials.  I agree that QB is running on the server and not locally.  In fact, in the original installation on this laptop, QB 16 wasn't even present on the workstation, though QB 14 was.

QB works fine for any proper user on the server with WSE out of the picture.  Keep in mind that it also works with WSE for any proper user on any other computer.

I would agree that Intuit is unlikely to want to discuss it at all because of WSE.
0
CompProbSolvAuthor Commented:
This has gotten even more odd.  After rebuilding the laptop and seeing the problem return, it went away.  The only thing of significance that I did was to log into the server (not through Remote Desktop) as the user, log into QB as the same user, and then exit.  I don't know if that caused it to work or if it was a coincidence.

I was able to reconnect with WSE several times without problems.  I only let it get to the main screen of QB as the error was showing up before that.

The client got the computer back and the problem is still there.  He is experiencing it when he tries to create a new invoice.  I hadn't tested that before.

I can use the same rdp file on my computer and log in with his credentials and create a new invoice without issue.

I'm back to the question of what it can be in the local computer that affects QB running remotely on the server.
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Brian BEE Topic Advisor, Independant Technology ProfessionalCommented:
As much as I love problems like this, I am thinking you are going to have to get support form the people who make this product. I mean, they are the ones who claim it will work, right?

Meanwhile, see if you can dial back the RDS settings as much as possible, like leave out printer and drive connections, for example. Anything that might tie the RDS session to the application.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
CompProbSolvAuthor Commented:
The problem never really went away.  What I hadn't recognized is that my test of whether or not I got to the desktop without error wasn't adequate.  Once I thought it was working I discovered that the failure came back when I tried to create an invoice or even to create a new data file.  The symptom was showing up immediately when I started this project likely because of the different windows that were open in QB at the start.

Nonetheless, I've given up on this one.  I'm really stuck on what it is that QB "knows" about my computer that makes the difference.  I thought it might be the screen resolution, but that didn't have any effect.  I set the laptop to 1280x1024 (which is what my other test systems are using) and it still had the problem.

Thanks for your suggestions.....
0
CompProbSolvAuthor Commented:
Wasn't able to resolve the problem.  Brian is correct that the solution needs to come from the software author.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.