Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Error Message on Small Business Server 2003

Updated: 21 May 2010 | 9 comments
Kin's picture
0 0 Votes
Login to vote
Just install the MR2 on Small Business Server 2003 R2 standard edition and deploy the antivirus/antispam and Network Threat Protection to it, however the following error prompt up :
 
Error : The resource file version does not match the version of the file trying to load it - cannot load SfManRes.dll
 
 
Error : The resource file version does not match the version of the file trying to load it - cannot load DevManRes.dll
 
After that, the Endpoint Protection cannot uninstall.
 
Anyone got the idea?
 
Kin

Comments

Kin's picture
14
Apr
2008
0 Votes 0
Login to vote

After stop all the necessary services, the client can be remove. However the EPS client still cannot install on SBS2003 R2 even only antispam and antivirus is selected.
Sandeep Cheema's picture
14
Apr
2008
0 Votes 0
Login to vote

See if you have these two dll's present in the %Program Files%\Symantec\Symantec Endpoint Protection\res\a numbered folder.
 
If you do, delete them and restart the client.
 
Also search the regitry for any instance for the dll.
 
Take a backup of the registry and delete these keys as well.
 
You just might have to restart  the client as we havent unregitered the dll's and try to install again.
 
If that doesnt halp, you may post couple a line's above the "return value 3" for SEP_INST.LOG over here which is in %TEMP%
 
 
 
 

De facto when AV does something, it starts jumping up and down, waving its arms, and shouting "Hey!  I found a virus!  Look at me!  I'm soooo goooood!"

Kin's picture
14
Apr
2008
0 Votes 0
Login to vote

Hi Sandeep,
 
Thanks for your help, however the problem still exist and the result is as follow:
 
1) Already delete the file located at  %Program Files%\Symantec\Symantec Endpoint Protection\res\a numbered folder (devmanres.dll and sfmanres.dll)
 
2) No registry key for the above dll was found
 
3) After reinstall the client, error still occur. There is no "return value 3" in the setup log and the SEP client can run. However the error prompt up each time the server reboot or the SEP client start.
 
4) One more thing is that both SEPM and SEP are installed on the same SBS server
 
Any idea?
 
Thanks



Message Edited by Kin on 04-14-2008 07:34 PM

Sandeep Cheema's picture
14
Apr
2008
0 Votes 0
Login to vote

My bad, I mistook it for an installation hiccup.
 
Two things that you can try :
 
1)If you are using NTP, Replace the dll from another client and then restarting the machine
 
2)If you are not using NTP, Search for teefer2 and see if any instance is present, delete any instance from the registry as well cause I think these two dll's acoount for the firewall.
 
 
 
 
 

De facto when AV does something, it starts jumping up and down, waving its arms, and shouting "Hey!  I found a virus!  Look at me!  I'm soooo goooood!"

Kin's picture
14
Apr
2008
0 Votes 0
Login to vote

I have uninstall the teefer2 driver from Network --> Local Area Connection Properties and then uninstall the EPS client. And then I search the "teefer2" keywords in the registry and then delete them.
 
After that I reinstall the EPS client which only included the Antivirus and Antispam. However same error still occur...
 
I would like to know is there any scripts that I can clearly remove the unwanted registry as the following steps is too risky and complex...
 
 
 



Message Edited by Kin on 04-14-2008 11:00 PM

Hamburg's picture
01
Jul
2008
0 Votes 0
Login to vote

Was this issue ever resolved?  I just upgraded a client to 11.0.2010.25 and am getting the same error message. "Resource file version does not match the version of the file trying to load it - cannot load SfManRes.dll"  Then, same message for DevManRes.dll.  Clicking through and acknowledging seems to work but the big question "Is it working?"  If so, how can I get rid of the error messages?

haroldg's picture
15
Oct
2008
0 Votes 0
Login to vote

Did this anyone ever get this resolved?

APIPA's picture
15
Oct
2008
0 Votes 0
Login to vote

I cleanwiped and reinstalled SEP on one of my test beds to fix this issue.

 

It may be different at your end. Could also be something environmental. 

Jeff4379's picture
18
Jun
2009
0 Votes 0
Login to vote

Solution

I was also experiencing this same issue.  I set all of the Symantec services to disabled, rebooted, and uninstalled. I actually had two concurrent versions installed, so there were a couple reboots and uninstalls involved.  After the final reboot I was able to reinstall without issue.