cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Former Member
Not applicable
Report Inappropriate Content
Message 1 of 12

Error EE050014: File access error

Having trouble on a Win XP SP3.

2 users are unable to log on, getting above error message. I can log in myself no problem.

Tried removing the users from the AD group - synching - waking agent - readding user to AD group - resyncing - waking agent. No help.

Running EEPC 6.1.

Read this from McAfee: http://webcache.googleusercontent.com/search?q=cache:uLXsCV_gN2wJ:https://kc.mcafee.com/corporate/in....

Under solution 1, it says to repair the PBFS using the EETech CD. I dont see any such option in the interface?

Any help is much appreciated.

11 Replies
Former Member
Not applicable
Report Inappropriate Content
Message 2 of 12

Re: Error EE050014: File access error

Hey....

I'm also facing this Issue. In my case i'm able to login with different user. this issue is only for particular user, i tried removing the users from the AD group - synching - waking agent - readding user to AD group - resyncing - waking agent. No help.

I'm also using EEPC 6.1

So please help....i refered all the KB's releted to ee050014 file access error but no luck.....

Former Member
Not applicable
Report Inappropriate Content
Message 3 of 12

Re: Error EE050014: File access error

Try removing the user assignment  from the machine in epo then sync wait for ee status monitor to tell you pOlicy has enforced then add user assignment back to machine and repeat sync.  This should remove the corrupt user file and then recreate it.

Also recommend upgrade to patch 2 imminently released which should prevent this error in future

Former Member
Not applicable
Report Inappropriate Content
Message 4 of 12

Re: Error EE050014: File access error

We have a machine with this exact same error.  Removing the user and epo, syncing the machine, and re-adding has not helped.  Actually, it doesn't seem to be applying any new policy from ePO because I tried changing the policy to decrypt and de-activate the machine and that's not working either. 

SafeBoot
Reliable Contributor
Reliable Contributor
Report Inappropriate Content
Message 5 of 12

Re: Error EE050014: File access error

Don_Martin
Level 11
Report Inappropriate Content
Message 6 of 12

Re: Error EE050014: File access error

Hello,

we have another Notebook which runs into this message. It is possible to remove users and to add users but the follwoing error message won´t disapear and specific user is not able to get further as EEPC-Authentification.

EEPC-Version 6.1.2.314

EEPC-Agent 1.1.2.314

It is a little bit frustrating to get knowledge of this error (which should be solved since version 6.1.1.x!)

Loglevel3 (on 12-02 user was able to work as usual and to authenticate at EEPC):

2011-12-02 07:11:58,857 WARNING MfeEpeUserLibService                 ..\..\..\Src\EpeUserLibServiceHandler.cpp: EPE_user_lib_service_handler::load_user_data: 89: [0xEE050014] Failed to read file

2011-12-02 07:11:58,857 WARNING MfeEpeUserLibService                 ..\..\..\Src\EpeUserLibServiceHandler.cpp: EPE_user_lib_service_handler::load_user_data: 94: [0xEE050014] Failed to read file

2011-12-02 07:12:00,131 WARNING MfeEpeEsEncryptionInformationService ..\..\..\Src\EpeFsmHostErrorHandler.cpp: EPE_fsm_host_error_handler::handle: 71: Received service unavailable exception: The service MfeEpeEncryptionInformationServiceClient is currently unavailable

2011-12-02 07:12:18,789 WARNING MfeEpeUserLibService                 ..\..\..\Src\EpeUserLibServiceHandler.cpp: EPE_user_lib_service_handler::load_user_data: 89: [0xEE050014] Failed to read file

2011-12-02 07:12:18,789 WARNING MfeEpeUserLibService                 ..\..\..\Src\EpeUserLibServiceHandler.cpp: EPE_user_lib_service_handler::load_user_data: 94: [0xEE050014] Failed to read file

2011-12-02 07:12:19,402 WARNING MfeEpeEsEncryptionInformationService ..\..\..\Src\EpeFsmHostErrorHandler.cpp: EPE_fsm_host_error_handler::handle: 71: Received service unavailable exception: The service MfeEpeEncryptionInformationServiceClient is currently unavailable

2011-12-02 07:32:00,047 WARNING MfeEpeEsEncryptionInformationService ..\..\..\Src\EpeFsmHostErrorHandler.cpp: EPE_fsm_host_error_handler::handle: 71: Received service unavailable exception: The service MfeEpeEncryptionInformationServiceClient is currently unavailable

2011-12-02 07:33:28,166 WARNING MfeEpeUserLibService                 ..\..\..\Src\EpeUserLibServiceHandler.cpp: EPE_user_lib_service_handler::load_user_data: 89: [0xEE050014] Failed to read file

2011-12-02 07:33:28,166 WARNING MfeEpeUserLibService                 ..\..\..\Src\EpeUserLibServiceHandler.cpp: EPE_user_lib_service_handler::load_user_data: 94: [0xEE050014] Failed to read file

2011-12-02 07:33:28,182 WARNING MfeEpeEsEncryptionInformationService ..\..\..\Src\EpeFsmHostErrorHandler.cpp: EPE_fsm_host_error_handler::handle: 71: Received service unavailable exception: The service MfeEpeEncryptionInformationServiceClient is currently unavailable

...

2011-12-02 07:41:34,663 INFO    EpoPlugin                            userHandler: processing user updates/requests

2011-12-02 07:41:34,773 WARNING MfeEpeGenEncryptionProviderPlugin    ..\..\..\Src\EpeGenUserHandler.cpp: EPE_gen_user_handler::get_updated_users: 353: [0xEE050014] Failed to read file

2011-12-02 07:41:34,820 INFO    EpoPlugin                            epoAudit: dispatching audits to AgentHandler

2011-12-02 07:41:34,991 ERROR   EpoPlugin                            userHandler: failed to perform user updates: [0xEE010002] [0xEE050014] Failed to read file

2011-12-02 07:41:34,991 INFO    EpoState                             == End of policy enforcement ==

2011-12-02 07:41:34,991 ERROR   MfeEpeStatusService                  Ein empfangener Benutzerdatenstapel konnte nicht verarbeitet werden

...

Loglevel3 (on 12-06 no more authentication with specific user credentials at EEPC possible):

2011-12-06 09:27:16,179 WARNING MfeEpeGenEncryptionProviderPlugin    ..\..\..\Src\EpeGenUserHandler.cpp: EPE_gen_user_handler::get_updated_users: 353: [0xEE050014] Failed to read file

2011-12-06 09:27:16,195 INFO    EpoPlugin                            epoAudit: dispatching audits to AgentHandler

2011-12-06 09:27:16,211 ERROR   EpoPlugin                            userHandler: failed to perform user updates: [0xEE010002] [0xEE050014] Failed to read file

2011-12-06 09:27:16,211 INFO    EpoState                             == End of policy enforcement ==

2011-12-06 09:27:16,211 ERROR   MfeEpeStatusService                  Ein empfangener Benutzerdatenstapel konnte nicht verarbeitet werden

2011-12-06 09:27:16,211 INFO    MfeEpeStatusService                  Durchsetzung von Richtlinien abgeschlossen

2011-12-06 09:29:38,111 WARNING MfeEpeEsEncryptionInformationService ..\..\..\Src\EpeFsmHostErrorHandler.cpp: EPE_fsm_host_error_handler::handle: 71: Received service unavailable exception: The service MfeEpeEncryptionInformationServiceClient is currently unavailable

2011-12-06 09:29:51,506 WARNING MfeEpeEsEncryptionInformationService ..\..\..\Src\EpeFsmHostErrorHandler.cpp: EPE_fsm_host_error_handler::handle: 71: Received service unavailable exception: The service MfeEpeEncryptionInformationServiceClient is currently unavailable

Loglevel4

2011-12-06 11:38:31,557 DEBUG   MfeEpeHost                           From uuid = 70e77e64-14e4-467d-8d22-775dc78d7c3b From Service = MfeEpeEncryptionService To uuid = 5b9302a2-1ffa-11e1-b7c6-58946b55bcc0 To Service = MfeEpeEncryptionServiceClient Message = <element xsi:type="ns1:ESGetUpdatedUsersExc"><sendTo xsi:type="ns1:MfeEpeAddress" serviceUUID="5b9302a2-1ffa-11e1-b7c6-58946b55bcc0" serviceName="MfeEpeEncryptionServiceClient"></sendTo><from xsi:type="ns1:MfeEpeAddress" serviceUUID="70e77e64-14e4-467d-8d22-775dc78d7c3b" serviceName="MfeEpeEncryptionService"></from><errorId>-301924350</errorId><message>[0xEE050014] Failed to uncompress user file</message></element>

2011-12-06 11:38:31,557 WARNING MfeEpeGenEncryptionProviderPlugin    ..\..\..\Src\EpeGenUserHandler.cpp: EPE_gen_user_handler::get_updated_users: 353: [0xEE050014] Failed to uncompress user file

2011-12-06 11:38:31,557 INFO    EpoPlugin                            epoAudit: dispatching audits to AgentHandler

2011-12-06 11:38:31,557 ERROR   EpoPlugin                            userHandler: failed to perform user updates: [0xEE010002] [0xEE050014] Failed to uncompress user file

2011-12-06 11:38:31,557 DEBUG   MfeEpeHost                           From uuid = B115AA20-0396-4F41-A230-F61AE50E1DF7 From Service =  To uuid =  To Service = MfeEpeStatusService Message = <element xsi:type="ns1:SSSendMessage"><sendTo xsi:type="ns1:MfeEpeAddress" serviceName="MfeEpeStatusService"></sendTo><serviceName>EpoPlugin</serviceName><message>Ein empfangener Benutzerdatenstapel konnte nicht verarbeitet werden</message><type>Error</type></element>

2011-12-06 11:38:31,557 ERROR   MfeEpeStatusService                  Ein empfangener Benutzerdatenstapel konnte nicht verarbeitet werden

2011-12-06 11:38:31,557 INFO    EpoState                             == End of policy enforcement ==

Former Member
Not applicable
Report Inappropriate Content
Message 7 of 12

Re: Error EE050014: File access error

I take it your client machine has been upgraded from 6.1 to 6.1 Patch 1 and then 6.1 Patch 2?

Any corruptions with the PBFS volume that may have happenned in the past will not be fixed with 6.1 Patch 2.

I would recommend if you keep getting this problem on a small number of notebooks that have been upgraded from a previous patch level that you carry out an emergency boot....this will rebuild the PBFS from scratch and you will see the problem no more from that point on since there will no corruptiosn to the filesystem from before your upgrades.

HTH, and if you follow this path, please let me know whether you see the problem after an emergency boot.

Don_Martin
Level 11
Report Inappropriate Content
Message 8 of 12

Re: Error EE050014: File access error

Hello,

yes you are definetly right.

So you suggest that every Notebook (like the one I mentioned) with normal behavier and any previous Version of EEPC must not be upgraded?!  Therefore every Notebook must get a new PBFS to prevent any corruptions due to the earlier Versions? If this is true I don´t know what to say...

Don´t get this wrong but the mentioned Notebook was not marked as problem, nor does any indication suggest the Update would go fatality wrong - how can I check wether or not the Notebook "could" crash the PBFS when their is no indication? The LogLevel3 entries were not there with the old Version and it is not affordable to query all LogFiles just before the update should take place 😕

Nachricht geändert durch Don_Martin on 06.12.11 06:55:45 CST
Former Member
Not applicable
Report Inappropriate Content
Message 9 of 12

Re: Error EE050014: File access error

I think you have misunderstood what I was saying.

I was definitely not saying that every notebook must get a new PBFS to prevent corruptions due to the earlier versions!  That would be untenable for our customers.

In general, the majority of PBFSs will not contain any corruptions, but some may, caused by (for example) powering off the machine or the OS killing off our service before we have had a chance to shut down properly (akin to you removing your USB memory stick part way through writing a file).

6.1.2 contains a new implementation of the pbfs filesystem library which has proven itself resilient to corruption in our extensive testing.   However, it cannot fix any corruptions in the file allocation tables of an existing PBFS during the upgrade process.

Therefore my recommendation is that if you have a problematic machine which appears to "retain" user corruption issues despite removing and re-adding the user as I suggested earlier in this thread, then go ahead and rebuild the PBFS using emergency boot on the problematic machine.

Any machine without corruption issues does not need any attention at all, except to keep it updated with the latest patch level.

I hope this explains things a bit more clearly!  Please shout if it doesn't!

Don_Martin
Level 11
Report Inappropriate Content
Message 10 of 12

Re: Error EE050014: File access error

Hello,

no I did not understood you wrong, I was just exaggerating (a little bit).

Maybe there is a affordable way to check wether or not there is an existing corruption? As i mentioned  I just do not like the idea to find out about a corrupt PBFS in a "Trial and Error" run and thereafter have to explain this to an employee nor does the employee wants to understand this in most cases.

Many thanks for your answer, I am not as good as I would like to in using proper english.

greetings

You Deserve an Award
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.

Community Help Hub

    New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.

  • Find Forum FAQs
  • Learn How to Earn Badges
  • Ask for Help
Go to Community Help

Join the Community

    Thousands of customers use the McAfee Community for peer-to-peer and expert product support. Enjoy these benefits with a free membership:

  • Get helpful solutions from McAfee experts.
  • Stay connected to product conversations that matter to you.
  • Participate in product groups led by McAfee employees.
Join the Community
Join the Community