Failed to load SCC module

[DanG83616]

Some of our users are getting "Error while initializing Version Control provider: Failed to load SCC module" when attempting to configure their project for version control. We have a README to guide then throught the process step-by-step and it has been working. Recently, two users are getting the error.

We are using Perforce version 2007.3 (problem also happens with 2008.1). Anyone have pointers for me?

Thanks,
Dan

[HowardB]

Hello Dan,

This error message is displayed when EA is unable to load the Version Control providers SCC client DLL.  This may indicate that the SCC client was not installed, or it may mean that it was not properly registered.  It could also mean that a DLL that the SCC client depends on could not be loaded.

Please check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders.  You should find an entry that names your VC provider and provides a reference to another registry key that specifies the path to the client DLL.

For example -  key: ...\InstalledSCCProviders\   Perforce SCM        value: SOFTWARE\Perforce\p4
                       key: ...\SOFTWARE\Perforce\p4\  SCCServerPath    value: C:\Program Files\Perforce\p4scc.dll


In the case where your SCC module cannot load because modules it depends on cannot be loaded, this is more difficult to identify and to resolve.   What used to be known as the SysInternals "Filemon" utility is extremely useful in this situation.  (It is a free download from Microsoft - a web search will find it...)  This will allow you to determine which modules cannot be found/loaded, so you can make the necessary corrections.

I hope this helps.

Regards,
Howard Britten.

[HowardB]

Hi All,

Dan has been kind enough to send me a follow up on this problem;

The P4 SCC plugin uses Qt (Trolltech) dlls, which it installs in the
P4 install tree.  Two of our users had installed another app (yet to be identified) that also uses Qt dlls. The other app installer placed the dlls in Windows\System32 directory. Windows looks there before looking in the P4 install tree and those dlls were not compatible with P4. Thus, P4's SCC plug-in wouldn't load and EA couldn't use it.

Thanks Dan  ...and I must say - well spotted.

regards,
Howard.