The application failed to initialize properly (0xc0000005) after installing SEP RU5 with application and Device Control.

[Migration User]

Issue:
The application failed to initialize properly (0xc0000005) after installing SEP RU5 .

Brief Explanation:
After Installing SEP RU5,When i tried to access this application ITIS.exe it shows an error called The application failed to initialize properly (0xc0000005),Click Ok to Terminate.

Steps Tried:
 I have uninstalled the Symantec End Point Protection it worked

 Reinstalled again same problem occurs

 I am using application and Device Control,i believe this issue is occuring, because of application and device control,however i would like to use Application and Device Control in my Clients to block USB.

Any Suggestions to fix this error message
 

[pete]

whaqt is the OS?

Install AV component and check if the error message is vanished?

[Migration User]

Symantec is aware of this issue and is currently  under investigation , i will update the thread when there is any update or progress on it.

[Migration User]

We've got the same issue with two of our important internal apps. Reverting to MR4 MP2 solves it for the moment... 

[Migration User]

Would it have been wise to remove the release if it is causing these issues? I now have 10 laptops that need to be reimaged...

[Migration User]

In my experience, there's no need to reimage the machine completely. Just uninstall SEP RU5 and install older version (i.e. MR4 MP2) and the issue is gone. (Or if you can live without Application and Device Control simply stop the sysplant service).
However, if this app is deployed enterprise-wide, I'd recommend to not further deploy the RU5 update.

[Migration User]

It has also been observed that if we disable the Application and Device control then it works fine, But off course this is not the solution for this issue, but this the work arround for this issue, hence Symantec is trying to find solution on this issue.

[Migration User]

This issue would be fixed in the next release of SEP

[Migration User]

Knowing this will be fixed in the next release does not up those of us who are suffering with this problem. In my case, I have installed it on several machines where the application error occurred and removed SEP 11 MR5 and the problem remained.

[Migration User]

There is no need to remove SEP, Just withdraw the application and device control policy. and you will be able to use the application

[Migration User]

I want to know whether the problem occur at Dell machine. Today I have the same error in my office.

[Migration User]

This issue is not specfic to modle of the machine or make.

The issue is caused due to conflict of application and device control policy with any aplication based on power builder and using sybase in the backend

[Migration User]

So does this issue occur if the default application and device comtrol is changed?  The only device policy I enabled the the useage of USB media storage and the issues doesn't occur on cleint earlier then RU5.

[Migration User]

 Prachand,

This issue is not limited to applications based on power builder and sybase and it can affect any application running on Windows. We are not Symantec customers but have ended up on this forum because one of the applications we produce is being crashed by SEP on our customers' PCs. SEP will crash any application where the application itself or a DLL loaded by the application has an image base on 0x10000000. Given that DLLs are dynamically loaded (hence the name) their image base changes and any DLL loaded by any application can potentially use 0x10000000. Neither our application nor any of its own DLLs is hard coded to use 0x10000000, however on some of our customers' PCs there are other DLLs that are loaded by all applications and it is one of those that is hitting 0x10000000. It is extremely serious that Symantec has released an application that does this and that the Windows OS allows this to happen. We are naturally infuriated that SEP is crashing our application and that Symantec has known about this problem for weeks but it has not been resolved.

Jon

[Migration User]

We're having the same problem on about 100 PC's.  Every time a PC boots up we have that box come up about 30 times (it's blocking our log on scripts and everything).  

SYMANTEC.  FIX YOU SOFTWARE.  THIS IS UNACCEPTABLE.  

 

[Migration User]

Title: 'After migrating a Symantec Endpoint Protection (SEP) 11 client to Release Update (RU) 5 or installing RU5, applications fail to initialize properly with error 0xc0000005, or 0xc0000018, or no error message.'
Document ID: 2009110612204948
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2009110612204948?Open&seg=ent

[Migration User]

When is this really going to be fixed?  The article you refer to does not note a timeframe.

Thank you. 

[Migration User]

It would be fixed in the next release, but still there isno time frame availbale right now

[ssi-udine]

we are experiencing the same problem here at City Council of Udine, Italy. we need badly a fix (all of ours sybase apps cannot work properly and fail with 0xc0000005 exception after the upgrade from SEP rel 10 to rel 11) but, reading this 3d, I've not seen any date of release for a patch or a fix, although the problem is marked as "solved". we'd like to hear some news from symantec ASAP.

berst regards

Paolo Agati


Comune di Udine - Dipartimento Affari Generali
Servizio Sistemi Informativi e Telematici
U.O. Gestione Forniture ICT

vox: [phone]
gsm: [phone]
skype: paolo.agati
mailto:[e-mail]

[Migration User]

This will be fixed in the next release of SEP. The date  for release has not been finalized. Once it is done I will post it here.

At this point of time the workaround is reverting back to MR4MP2 or Withdrawing the Application and Device control policy

[Migration User]

I have only experienced this on Dell Latitude D-Series laptops, we are currently running full SEP 11.5002 on all endpoints. I have noticed it depends on how the client is installed, whether it is exported in a package and run manually or pushed from policy. It only affects us is when it is assigned through policy as a package and automatically pushed out. To work around it I just uninstalled the 11.5002 client and reinstalled with only AV and AS components. 


Side Note -  I'm used to this kind of stuff, now if a user calls about anything I know where to look. Control Panel , Add Remove Programs, Symantec Endpoint Protection, Uninstall.

[Migration User]

I'm a package software programmer.
My all applications cannot be run on SEP !!

I'm still waiting this fix...

** Please release it ASAP **

[ℬrίαη]

You can uninstall the Application and Device control component until the next version of SEP is released. Doing this will fix your problem.

[Migration User]

we are having the same problem on the Dell laptops also. and we found that the SEP client device control component is having conflict with the EMBASSY Trust Suite which is come from Dell laptop. after we uninstall the software, the problem solved.

[Migration User]

The fix for the issue is resolved. Please contact support and get the new build SEP 11.0.5 PP1.

A fix for this issue has been released in SEP 11.0 RU5 PP1 (Point Patch 1). This is a client-only build (11.0.5024.404) which is supported only when freshly installed or migrated over SEP 11 RU5 (11.0.5002.333).

[ℬrίαη]

Will there be any issues since the SEPM is on a different release or does that not matter as long as it's 11.0.5xxx.xxx?

[Migration User]

There  will be no issues . You just need to add the Package in SEPM and push the packge from there.

[ℬrίαη]

Just called support. They said it was not yet available as it was still in testing.....

[Migration User]

The Embassy Trust Suite issue is resolved by updating Embassy Trust itself... it was an issue with an outdated version of wxvault.dll.  See the following if the error code matches the one you're seeing:

Title: 'Error: "The application failed to initialize properly (0xc000007b). Click on OK to terminate the application" on Symantec Endpoint Protection clients with Application and Device Control enabled.'
Document ID: 2008022914263148
> Web URL: http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008022914263148

sandra

[Migration User]

Hi Support,

We have got the same issue also, we have one of the application (Sybase PB DLL + ODBC + Share exe from Server) and shortcut for all user, and now over 70% user was unable to run the application into their computer after install the latest SEP... and we didn't have the Application and Device Control policy, so would you please help to fix it ASAP? Thanks !

B. Regards,
Alex

[Migration User]

i am experiancing the same problem in my company to. 30 Pcs and laptops till now and rising,,,:((

how can i get the new build SEP 11.0.5 PP1. is it available via fileconnect?

[Migration User]

No, For that you have to contact support on our local suuport no. log a case and then only you can get the SEP RU5 PP1.

http://www.symantec.com/business/support/contact_techsupp_static.jsp

[Migration User]

i've opend a case in symantec and the technician that was asinged to my problem is totaly clueless.... :((
I've spend two days teling him what i need, and he cannot give me the patch. after 3 hours i convinced him to find me a link to some ftp server from which i can download the PP1, but the credential does not work.

does anyone have this patch somewhere and can i get it.
This is totaly crazy, spending 7hours on the telephone with a support that cannot provide me with a simple valid ftp credentials for donwloading a patch

[Migration User]

RU6 also includes the fix that the patch addresses.  This is now available via Fileconnect.

sandra

[Migration User]

i've actually discovered that.
i gues the symantec people have put it on the fileconnect the next day after i've tried to get it (the 14th) :))

thanks anyway

[Migration User]

Yes it is now fixed in the Symantec Endpoint Protection version: 11.0.6000.550 :-)

Cheers.