"Failed to launch Fantasy Grounds"

[cfrolik]

After installing the Fantasy Grounds Unity version from Steam, and clicking "Launch Fantasy Grounds", the FGUpdaterEngine app just tells me "Failed to Launch Fantasy Grounds". Clicking the Log button doesn't help much either, since the log file it opens contains that same error text, but not much else that would be useful.

What other information can I provide to help debug this problem?

[cfrolik]

Something that might be helpful....
I opened C:\Program Files\SmiteWorks\Fantasy Grounds\FGUpdaterEngine.log
and found this:


e: SaveFile - System.UnauthorizedAccessException: Access to the path "C:\Program Files\SmiteWorks\Fantasy Grounds\FantasyGrounds.exe" is denied.
at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize, System.Boolean anonymous, System.IO.FileOptions options) [0x0019e] in <fb001e01371b4adca20013e0ac763896>:0
at System.IO.FileStream..ctor (System.String path, System.IO.FileMode mode, System.IO.FileAccess access, System.IO.FileShare share, System.Int32 bufferSize) [0x00000] in <fb001e01371b4adca20013e0ac763896>:0
at (wrapper remoting-invoke-with-check) System.IO.FileStream..ctor(string,System.IO.FileMo de,System.IO.FileAccess,System.IO.FileShare,int)
at System.IO.File.Create (System.String path, System.Int32 bufferSize) [0x00000] in <fb001e01371b4adca20013e0ac763896>:0
at System.IO.File.Create (System.String path) [0x00000] in <fb001e01371b4adca20013e0ac763896>:0
at FileManager.SaveStreamToFile (System.IO.Stream str, System.String sFile, Ionic.Zip.ZipFile zf, System.Collections.Generic.List`1[T] fileStreams, System.String sProduct) [0x00037] in <ece7fe0749074783ba5a7fe4b177ce7b>:0
HandleFile: Unable to save file (FantasyGrounds.exe)
i: C:\Program Files\SmiteWorks\Fantasy Grounds\UnityPlayer.dll
UnzipProduct-FantasyGrounds: 3.6417692
FantasyGrounds Update Complete
Validating packages...
19 products checked

[cfrolik]

Well, this is embarrassing.
Rebooting and updating again fixed it.

[damned]

Hah. Its not embarrasing. Its annoying. But great news too!
Well doen and thanks for posting the fix in your case.