Problems Upgrading

[DrakosDJ]

I have been trying to get the updates to v3.1.15 for the last several days but unsuccessfully. The update keeps getting timeout errors and then eventually fails with this message:

SaveToVault

Unable to extract file (extensions/5E_Theme_Wizards.ext)
HandleFile

Unable to save file (extensions/5E_Theme_Wizards.ext) to content vault.
Error during update check

It doesn't fail on the same file each time, sometimes it is on an early file and others it goes quite some time (up to 30 minutes) before it fails. Usually with several timeout errors before failing. This behavior actually started with 3.1.14, but it eventually loaded.

[JohnD]

Delete content.dat and content.dat.tmp (if it exists) and run your update again.

[DrakosDJ]

Delete content.dat and content.dat.tmp (if it exists) and run your update again.

Thank you for the suggestion, but unfortunately it didn't help. I continue to have the same issues.

[Moon Wizard]

These error messages mean that Fantasy Grounds is unable to write files to the location specified. These errors are usually caused by the FG installer/updater not having the correct operating system permissions.

Did you use the default data directory folder (i.e. C:\Users\<User>\AppData\Roaming\Fantasy Grounds\), or choose another location?
If another location was chosen, then this is a likely cause, since programs are not allowed to freely write data to disk except in very specific locations denoted by the operating system.

Are you running the updater as administrator?
This will usually bypass the issue, as running as administrator should give the updater full rights to write to any disk location. There are certain scenarios where you have to actually log in as administrator user, depending on your operating system setup.

Regards,
JPG

[DrakosDJ]

Moon Wizard,

I used the default path (what you posted) and the account has Administrator rights. Also, it didn't always die at the same spot, and you could see the content.dat.tmp file would be different sizes depending on how far it got. There were a lot of Connection timeout errors as well.

After about 50 tries, it finally loaded. The last update session took several hours and had quite a few timeout errors, but it loaded.

Thanks for the response.

[midas]

I had this problem yesterday when I was installing FG on my machine at work to test out something for another user. I installed FG to the default location (from website download), entered my key information and it would randomly die on various things that write to the protected vault. It didn't seem to matter if I launched FG as an administrator or not, but I'm wondering if it's because UpdaterEngine.exe may have been called and *wasn't* inheriting that permission.

Ultimately I just changed the install and data directory to another folder (C:\Low Security Installs) and the entire process completed without issue.

[Moon Wizard]

DrakosDJ,

If you are having a lot of timeout issues, and it's taking a long time; my guess is that your Internet connection is not very strong and you are getting a lot of packet loss. The updater does not handle adverse networking conditions very well (and won't until we replace the entire networking backend next year). Try plugging your computer directly into the router during updates to improve the situation.

Regards,
JPG

[DrakosDJ]

DrakosDJ,

If you are having a lot of timeout issues, and it's taking a long time; my guess is that your Internet connection is not very strong and you are getting a lot of packet loss. The updater does not handle adverse networking conditions very well (and won't until we replace the entire networking backend next year). Try plugging your computer directly into the router during updates to improve the situation.

Regards,
JPG

I am plugged directly in, and I am getting good network connectivity, at leas as far as I can detect. If you give me a server to ping I can tell you what I get.

[damned]

I am plugged directly in, and I am getting good network connectivity, at leas as far as I can detect. If you give me a server to ping I can tell you what I get.

try this one... 74.208.1.229

[DrakosDJ]

Ok, I pinged: 74.208.1.229 and the results were not good. I tried twice just to be sure and here is what I got.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>ping 74.208.1.229

Pinging 74.208.1.229 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.208.1.229:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Administrator>ping 74.208.1.229

Pinging 74.208.1.229 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 74.208.1.229:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Administrator>

So, apparently my connection to that server has issues.

[Trenloe]

Ok, I pinged: 74.208.1.229 and the results were not good. I tried twice just to be sure and here is what I got.
I can't ping it either, so it looks like pings are blocked to that server.

[damned]

Ok, I pinged: 74.208.1.229 and the results were not good. I tried twice just to be sure and here is what I got.

...

So, apparently my connection to that server has issues.

Sorry DrakosDJ try this IP - 74.208.193.1

[DrakosDJ]

No problem. So I ping'ed the 74.208.193.1 and here are my results:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>ping 74.208.193.1

Pinging 74.208.193.1 with 32 bytes of data:
Reply from 74.208.193.1: bytes=32 time=129ms TTL=54
Reply from 74.208.193.1: bytes=32 time=449ms TTL=54
Reply from 74.208.193.1: bytes=32 time=453ms TTL=54
Reply from 74.208.193.1: bytes=32 time=393ms TTL=54

Ping statistics for 74.208.193.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 129ms, Maximum = 453ms, Average = 356ms

C:\Users\Administrator>