R56.9 - Cannot Authorize Quicken Classic after Update
Windows 10; Quicken Classic Version R56.9 Build 27.1.56.9
I updated Quicken Classic yesterday and after it completed, it asked me to authorize using my Quicken ID. I entered my credentials and I get an error indicating it is unable to contact the Quicken server.
Specifically I get an error window that says: "Oops! Something went wrong.
We are unable to contact the Quicken server. This is usually temporary. Please try again in one hour. If this problem persists, please contact Quicken Support."
I have tried multiple times over the past two days and have been unsuccessful; I even tried reinstalling with the same result.
This is the last entry in the QuickenAuthorizationLog.txt:
qw PID(31844) TID(1) 27.1.56.9 5/1/24 3:11:57:460 PM ERROR Quicken.Services.Authentication.OAuth2Service "QAM.Authorization.NetworkCommunicationException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
--- End of inner exception stack trace ---
at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)
--- End of inner exception stack trace ---
at System.Net.WebClient.UploadDataInternal(Uri address, String method, Byte[] data, WebRequest& request)
at System.Net.WebClient.UploadData(Uri address, String method, Byte[] data)
at QAM.Authorization.AuthorizationClient.SignInWithWebAuthorizationResponse(Uri responseUri, Uri IUSServerBaseURL)
--- End of inner exception stack trace ---
at QAM.Authorization.Internal.Transactions.HttpTransaction.HandleResponseError(Exception exception)
at QAM.Authorization.Internal.Transactions.RequestAccessTokenFromAuthCode.RequestAccessTokenFromAuthCodeTransaction.HandleResponse(Exception exception)
at QAM.Authorization.AuthorizationClient.SignInWithWebAuthorizationResponse(Uri responseUri, Uri IUSServerBaseURL)"
Any help resolving this problem would be appreciated.
Comments
-
Have you tried logging off and logging on as a new user?
0 -
@ARoteliuk - here are some suggestions from Copilot -
If Quicken is not connecting to the Internet, there could be several reasons. Here are some troubleshooting steps you can take:
- Check for a Specific Error Number: If you’re seeing an error message, look for a specific error number and search for it on the Quicken support site1.
- Connection Speed: Ensure your internet connection speed is at least 25Mbps, as Quicken requires this for proper functionality1.
- Secure Connection: Verify that your web browser can establish a secure connection1.
- Security and Privacy Programs: Check if security programs like firewalls and pop-up blockers are configured correctly1.
- Router Configuration: If you’re using a router, try connecting your computer directly to your modem to see if Quicken connects. If it does, you may need to configure your router or update its software2.
- Quicken ID Sign-in: Try signing out and signing back into your Quicken ID. Go to Edit -> Preferences -> Quicken ID, sync & alerts, and follow the prompts to sign in again3.
- Update Quicken: If you’re using an older version of Quicken, such as Quicken 2017, you might need to download and apply the latest update patch4.
If these steps do not resolve the issue, you may want to reach out to Quicken’s customer support for further assistance. Remember to keep your software up to date and regularly check for any updates or patches that may improve connectivity.
Item #6 is what @RalphC suggested and the first thing I would try. If none of these suggestions resolve your issue, I would contact Quicken Support.
Additional suggestions from Copilot -
If Quicken is unable to contact its servers, it could be due to a variety of issues. Here are some steps you can take to troubleshoot the problem:
- Check Internet Connection: Ensure your internet connection is stable and active.
- Windows Defender Settings: If you have Windows Defender’s Controlled Folder Access feature enabled, it might prevent Quicken from communicating with its servers. You should configure it to add Quicken as an “allowed app” without turning off Ransomware protection1.
- Quicken Server Status: Sometimes the issue might be on Quicken’s end. Check if there are any notifications about server maintenance or downtime.
- Firewall and Antivirus: Make sure your firewall or antivirus settings are not blocking Quicken. You may need to set exceptions for Quicken in these programs.
- Update Quicken: Ensure you have the latest version of Quicken installed. Outdated versions may have trouble connecting to the servers.
- Reinstall Quicken: If none of the above solutions work, try reinstalling Quicken. Make sure to back up your data before doing so.
If the issue persists after trying these steps, it would be best to contact Quicken support for further assistance. They can provide more detailed guidance based on the specific details of your situation. Remember to provide them with any error messages you’re seeing, as this can help diagnose the problem more quickly.
Bottom line, if the error persists, then contacting Quicken Support is your best option.
0 -
Appreciate the responses. I've tried pretty much everything suggested except for connecting my computer directly to the cable modem and only because that's such a pain to do and everything else works on my network including logging into my financial institution.
I just tried creating a new Quicken account and starting a new Quicken file with it and I get the same result except I was sent a verification code to enter before I get the "Oops! Something went wrong." window. It almost seems like the Quicken server is the problem but I don't see that reported anywhere.
I also have the same kind of problem when I try to report the problem through the Quicken "Report a problem…" Help menu item. It's a different popup window that says "Unable to send report to Quicken, please try again."
0 -
@ARoteliuk sorry that you haven't found a solution to your issue. If nothing you have tried has worked so far, I think your next step, if you haven't done so already, is to contact Quicken Support.
If you do contact them and they provide a solution to your issue, if you wouldn't mind circling back and sharing that would be great. I have noticed that you aren't the only one with this issue, but there doesn't seem to be a documented solution.
Good luck!
0 -
Well this community forum is supposedly one way to contact Quicken Support ("Get help from our expert users and customer support team. Available 24/7."), so that's why I started here, hoping customer support will read and indicate if there's something more I need to do to help them.
Next thing I did was use Revo Uninstaller to remove a lot of the remnants Quicken leaves behind when uninstalled, rebooted my computer and installed Quicken fresh. Now after asking for my Quicken ID credentials it asks for a 6-digit code it sends to my email, and when I enter that I now get the "Oops! Something went wrong." window. So Quicken is able to communicate well enough to send me a verification code via email, but not well enough to verify my application? I'm not buying it's on my end, so I hope customer support will post here indicating what they are doing for a solution.
0 -
Well I guess it's actually something off with my main computer; I was able to install on an old laptop and it authenticates fine with the Quicken ID. Oh well…
0 -
@ARoteliuk There might be another way to resolve your issue. Take a look at the attached thread. Your issue is similar and maybe some of the suggest will work for you.
Otherwise, maybe reinstalling Windows on your main computer, might work? It definitely could be a Windows installation or settings issue.
0 -
Appreciate the help, but none of that changed the problem. I don't suppose there's any way to manually authorize Quicken or some other way to get it to bypass that screen? I'd like to know if everything else about Quicken and my data file are still working, like transaction downloads etc. It's very strange that everything else but Quicken is working on this computer. I'm not going through the hassle of reinstalling Windows just because of Quicken yet. In the meantime I've signed up for a 45 day free trial of [Removed - 3rd Party Software] and have uploaded my Quicken data; unfortunately [Removed - 3rd Party Software] doesn't track investment transactions (only overall value), but I suppose I never paid close attention to them anyway.
0 -
For any tech nerds out there especially at Quicken Support, I captured the packet traffic while trying to authorize Quicken via Wireshark. Near the end there appear to be two successful communications to services.quicken.com and signin.quicken.com then seemingly four failed connections to services.quicken.com where it looks like my computer immediately aborts a connection after the three-way handshake to establish the connection:
No. Time Source Destination Protocol Length Info
2308 28.147969 192.168.1.202 52.43.4.130 TCP 66 59344 → 443 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
2311 28.189231 52.43.4.130 192.168.1.202 TCP 66 443 → 59344 [SYN, ACK] Seq=0 Ack=1 Win=26883 Len=0 MSS=1460 SACK_PERM WS=256
2312 28.189324 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [ACK] Seq=1 Ack=1 Win=262656 Len=0
2313 28.192235 192.168.1.202 52.43.4.130 TLSv1.2 658 Client Hello (SNI=services.quicken.com)
2315 28.231307 52.43.4.130 192.168.1.202 TCP 60 443 → 59344 [ACK] Seq=1 Ack=605 Win=28160 Len=0
2316 28.232207 52.43.4.130 192.168.1.202 TLSv1.2 1514 Server Hello
2317 28.233151 52.43.4.130 192.168.1.202 TCP 1514 443 → 59344 [ACK] Seq=1461 Ack=605 Win=28160 Len=1460 [TCP segment of a reassembled PDU]
2318 28.233151 52.43.4.130 192.168.1.202 TLSv1.2 602 Certificate, Server Key Exchange, Server Hello Done
2319 28.233191 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [ACK] Seq=605 Ack=2921 Win=262656 Len=0
2320 28.234395 192.168.1.202 52.43.4.130 TLSv1.2 180 Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message
2321 28.234462 192.168.1.202 52.43.4.130 TLSv1.2 153 Application Data
2322 28.234569 192.168.1.202 52.43.4.130 TLSv1.2 468 Application Data
2324 28.277457 52.43.4.130 192.168.1.202 TCP 60 443 → 59344 [ACK] Seq=3469 Ack=1244 Win=29440 Len=0
2325 28.277457 52.43.4.130 192.168.1.202 TLSv1.2 225 New Session Ticket, Change Cipher Spec, Encrypted Handshake Message
2326 28.277457 52.43.4.130 192.168.1.202 TLSv1.2 132 Application Data
2327 28.277601 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [ACK] Seq=1244 Ack=3718 Win=261888 Len=0
2328 28.277751 192.168.1.202 52.43.4.130 TLSv1.2 92 Application Data
2329 28.278723 52.43.4.130 192.168.1.202 TLSv1.2 404 Application Data
2330 28.279500 192.168.1.202 52.43.4.130 TLSv1.2 305 Application Data
2345 28.321286 52.43.4.130 192.168.1.202 TCP 60 443 → 59344 [ACK] Seq=4068 Ack=1533 Win=30720 Len=0
2350 28.327462 52.43.4.130 192.168.1.202 TLSv1.2 581 Application Data
2351 28.327462 52.43.4.130 192.168.1.202 TLSv1.2 102 Application Data
2352 28.327462 52.43.4.130 192.168.1.202 TLSv1.2 92 Application Data
2353 28.327569 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [ACK] Seq=1533 Ack=4643 Win=262656 Len=0
2368 28.378603 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [ACK] Seq=1533 Ack=4681 Win=262656 Len=0
2392 30.118600 192.168.1.202 52.43.4.130 TLSv1.2 190 Application Data
2393 30.159840 52.43.4.130 192.168.1.202 TLSv1.2 422 Application Data
2394 30.160926 192.168.1.202 52.43.4.130 TLSv1.2 235 Application Data
2395 30.160960 192.168.1.202 52.43.4.130 TLSv1.2 380 Application Data
2396 30.202598 52.43.4.130 192.168.1.202 TCP 60 443 → 59344 [ACK] Seq=5049 Ack=2176 Win=34304 Len=0
2423 32.523115 52.43.4.130 192.168.1.202 TLSv1.2 933 Application Data
2424 32.523289 52.43.4.130 192.168.1.202 TLSv1.2 102 Application Data
2425 32.523289 52.43.4.130 192.168.1.202 TLSv1.2 92 Application Data
2426 32.523362 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [ACK] Seq=2176 Ack=5976 Win=261376 Len=0
2441 32.576306 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [ACK] Seq=2176 Ack=6014 Win=261376 Len=0
2510 34.226426 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [FIN, ACK] Seq=2176 Ack=6014 Win=261376 Len=0
2518 34.266378 52.43.4.130 192.168.1.202 TCP 60 443 → 59344 [FIN, ACK] Seq=6014 Ack=2177 Win=34304 Len=0
2519 34.266457 192.168.1.202 52.43.4.130 TCP 54 59344 → 443 [ACK] Seq=2177 Ack=6015 Win=261376 Len=0No. Time Source Destination Protocol Length Info
2427 32.535921 192.168.1.202 18.164.154.80 TCP 66 59350 → 443 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
2430 32.552052 18.164.154.80 192.168.1.202 TCP 66 443 → 59350 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1440 SACK_PERM WS=512
2431 32.552147 192.168.1.202 18.164.154.80 TCP 54 59350 → 443 [ACK] Seq=1 Ack=1 Win=263424 Len=0
2432 32.554854 192.168.1.202 18.164.154.80 TLSv1.3 744 Client Hello (SNI=signin.quicken.com)
2433 32.571088 18.164.154.80 192.168.1.202 TCP 60 443 → 59350 [ACK] Seq=1 Ack=691 Win=67072 Len=0
2434 32.572052 18.164.154.80 192.168.1.202 TLSv1.3 1494 Server Hello, Change Cipher Spec, Application Data
2435 32.572100 18.164.154.80 192.168.1.202 TCP 1494 443 → 59350 [PSH, ACK] Seq=1441 Ack=691 Win=67072 Len=1440 [TCP segment of a reassembled PDU]
2436 32.572141 192.168.1.202 18.164.154.80 TCP 54 59350 → 443 [ACK] Seq=691 Ack=2881 Win=263424 Len=0
2437 32.572661 18.164.154.80 192.168.1.202 TLSv1.3 1378 Application Data, Application Data, Application Data
2438 32.573735 192.168.1.202 18.164.154.80 TLSv1.3 118 Change Cipher Spec, Application Data
2439 32.573828 192.168.1.202 18.164.154.80 TLSv1.3 146 Application Data
2440 32.573911 192.168.1.202 18.164.154.80 TLSv1.3 1225 Application Data
2442 32.585459 18.164.154.80 192.168.1.202 TCP 60 443 → 59350 [ACK] Seq=4205 Ack=755 Win=67072 Len=0
2443 32.585459 18.164.154.80 192.168.1.202 TCP 60 443 → 59350 [ACK] Seq=4205 Ack=847 Win=67072 Len=0
2444 32.585459 18.164.154.80 192.168.1.202 TCP 60 443 → 59350 [ACK] Seq=4205 Ack=2018 Win=70144 Len=0
2445 32.585524 18.164.154.80 192.168.1.202 TLSv1.3 200 Application Data
2446 32.585607 18.164.154.80 192.168.1.202 TLSv1.3 125 Application Data
2447 32.585638 192.168.1.202 18.164.154.80 TCP 54 59350 → 443 [ACK] Seq=2018 Ack=4422 Win=263424 Len=0
2448 32.585748 192.168.1.202 18.164.154.80 TLSv1.3 85 Application Data
2450 32.638553 18.164.154.80 192.168.1.202 TCP 60 443 → 59350 [ACK] Seq=4422 Ack=2049 Win=70144 Len=0
2451 32.833698 18.164.154.80 192.168.1.202 TCP 1494 443 → 59350 [ACK] Seq=4422 Ack=2049 Win=70144 Len=1440 [TCP segment of a reassembled PDU]
2452 32.833698 18.164.154.80 192.168.1.202 TLSv1.3 991 Application Data
2453 32.833698 18.164.154.80 192.168.1.202 TLSv1.3 85 Application Data
2454 32.833920 192.168.1.202 18.164.154.80 TCP 54 59350 → 443 [ACK] Seq=2049 Ack=6799 Win=263424 Len=0
2455 32.883852 192.168.1.202 18.164.154.80 TCP 54 59350 → 443 [ACK] Seq=2049 Ack=6830 Win=263424 Len=0
2509 34.226301 192.168.1.202 18.164.154.80 TCP 54 59350 → 443 [FIN, ACK] Seq=2049 Ack=6830 Win=263424 Len=0
2513 34.241390 18.164.154.80 192.168.1.202 TCP 60 443 → 59350 [FIN, ACK] Seq=6830 Ack=2050 Win=70144 Len=0
2514 34.241475 192.168.1.202 18.164.154.80 TCP 54 59350 → 443 [ACK] Seq=2050 Ack=6831 Win=263424 Len=0No. Time Source Destination Protocol Length Info
2477 33.717109 192.168.1.202 52.43.4.130 TCP 66 59353 → 443 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
2478 33.760217 52.43.4.130 192.168.1.202 TCP 66 443 → 59353 [SYN, ACK] Seq=0 Ack=1 Win=26883 Len=0 MSS=1460 SACK_PERM WS=256
2479 33.760371 192.168.1.202 52.43.4.130 TCP 54 59353 → 443 [ACK] Seq=1 Ack=1 Win=262656 Len=0
2480 33.760466 192.168.1.202 52.43.4.130 TCP 54 59353 → 443 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
2481 33.760504 192.168.1.202 52.43.4.130 TCP 54 59353 → 443 [RST, ACK] Seq=1 Ack=1 Win=0 Len=02482 33.761253 192.168.1.202 52.43.4.130 TCP 66 59354 → 443 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
2483 33.803223 52.43.4.130 192.168.1.202 TCP 66 443 → 59354 [SYN, ACK] Seq=0 Ack=1 Win=26883 Len=0 MSS=1460 SACK_PERM WS=256
2484 33.803353 192.168.1.202 52.43.4.130 TCP 54 59354 → 443 [ACK] Seq=1 Ack=1 Win=262656 Len=0
2485 33.803445 192.168.1.202 52.43.4.130 TCP 54 59354 → 443 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
2486 33.803481 192.168.1.202 52.43.4.130 TCP 54 59354 → 443 [RST, ACK] Seq=1 Ack=1 Win=0 Len=02487 33.932747 192.168.1.202 52.43.4.130 TCP 66 59356 → 443 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
2490 33.972283 52.43.4.130 192.168.1.202 TCP 66 443 → 59356 [SYN, ACK] Seq=0 Ack=1 Win=26883 Len=0 MSS=1460 SACK_PERM WS=256
2491 33.972371 192.168.1.202 52.43.4.130 TCP 54 59356 → 443 [ACK] Seq=1 Ack=1 Win=262656 Len=0
2492 33.972475 192.168.1.202 52.43.4.130 TCP 54 59356 → 443 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
2493 33.972508 192.168.1.202 52.43.4.130 TCP 54 59356 → 443 [RST, ACK] Seq=1 Ack=1 Win=0 Len=02494 33.973067 192.168.1.202 52.43.4.130 TCP 66 59357 → 443 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
2496 34.009328 52.43.4.130 192.168.1.202 TCP 66 443 → 59357 [SYN, ACK] Seq=0 Ack=1 Win=26883 Len=0 MSS=1460 SACK_PERM WS=256
2497 34.009445 192.168.1.202 52.43.4.130 TCP 54 59357 → 443 [ACK] Seq=1 Ack=1 Win=262656 Len=0
2498 34.009530 192.168.1.202 52.43.4.130 TCP 54 59357 → 443 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0
2499 34.009564 192.168.1.202 52.43.4.130 TCP 54 59357 → 443 [RST, ACK] Seq=1 Ack=1 Win=0 Len=00 -
Well, I finally figured it out. It ended up being caused by Kaspersky Anti-Virus; even if I disabled it. I updated to their current product Kaspersky Standard (which kept my license duration from KAV) and now Quicken (and a few other weird network things) now are fine.
0
