nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Wells Fargo Connection Issues

Hank Sutherland

For two days now I have been getting the message when attempting a One Step Update:

Connections are blocked from $scheduleStartDate $scheduleStartTime EDT to $scheduleEndDate $scheduleEndTime EDT. You'll be able to reconnect after this time.

I get the same message when attempting an individual account update. I have never seen this message before. What does this mean?

Find more posts tagged with

One Step Update

Comments

thorn5

I am having the very same issue. Please advise.

thorn5

See attached…

Screenshot 2025-03-16 090433.png

Quicken Jasmine

Hello @Hank Sutherland and @thorn5,

Thanks for reaching out!

This is a known issue that has been reported, our teams are looking into this and working on getting it resolved. However, our development team also believes that this is a problem in the runtime.dat file, and recommends the following steps below to correct this issue.

First, please run One Step Update. If the issue persists, follow these steps:

1. Rename the runtime.dat file found at C:\ProgramData\Quicken\Inet\FILENAME\. (For example, add a 1 at the start of the file name, so that it reads 1runtime.dat.)

2. Run a One Step Update (OSU) again to confirm the issue is resolved.

Note - The Program Data folder is hidden by default. If you need instructions on unhiding the folder, you can find instructions on Microsoft's support site.

Please let me know how it goes!

(CTP-12393)

lecleclec

I just tried the suggested rename and no longer get that error message. (Connections are blocked from $scheduleStartDate etc….)

This is what I did: Found runtime.dat here: C:\ProgramData\Quicken\Inet\QDATA

Renamed it to 1runtime.dat as advised. Ran an One Time Update and it worked fine. A new runtime.dat was created. I reran the update and that worked as well. yay!