Posted 12 April 2017 - 09:07 AM
I had some trouble with P4A, so yesterday I updated everything to the newest version.
Now, when I try to open P4A, P4V and P4Merge I get the following error message:
"Error initializing Helix Visual Client.
Unable to load resource file."
P4A opens after the error, but icons don't display, P4Merge seems to open OK, and P4V doesn't open at all (and that's my biggest problem).
I tried doing the repair installation, but it didn't help.
Is there a way of fixing it without having to reinstall the whole thing?
P4A version: 2017.1/1491634
Thanks for help.
Posted 12 April 2017 - 05:08 PM
Current revision: Rev. P4Admin/NTX64/2017.1/1491634
Anyone have any idea what's causing this?
Posted 18 April 2017 - 01:17 PM
Posted 18 April 2017 - 01:35 PM
Might be worth running procmon (https://technet.micr...essmonitor.aspx) to see what P4V is looking for and if any errors. You can filter by p4v.exe and status.
"It's wonderful to see a new book about Perforce, especially one written by Robert Cowham and Neal Firth. No one can teach Perforce better than these seasoned subject matter experts"
- Laura Wingerd, author of Practical Perforce, former VP of Product Technology at Perforce
Posted 20 April 2017 - 02:49 PM
I'm not particularly savvy to thread-based investigations (I've only done it a few times in the past), so is there anyone that can make sense of all this? I'd like to get to the root of this if possible. Since there is no 'technical support/discussion' area, might as well do it here!
Posted 20 April 2017 - 04:33 PM
Posted 16 May 2017 - 03:06 PM
I suppose it's a lock / permissions issue.
Run with administrator privilege (right click -> "Run as Administrator") both installer and P4V.
Did the job for me.
Posted 01 June 2017 - 05:22 PM
C:\Program Files (x86)\Perforce\P4VResources\images.rcc
I'm guessing this is a 64 bit client install over an existing x86/win32/32 bit installation bug, which installs the 64 bit client into the existing install location under 'Program Files (x86)', but puts images.rcc into 'Program Files' just for laughs.
Also tagged with one or more of these keywords: error, bug, resource file
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users