PHP IDE :: NuSphere Forums :: View topic

Posted: Tue Jun 21, 2005 7:21 pm

Trying to start phped and now I get the error message:

Security initialization failed.

Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initiliazed.

Any idea what this means and how to fix it?

Thanks,
Jeff

Posted: Wed Jun 22, 2005 10:54 am

Definitely, this message is not from PHPED.
Could you please contact support AT nusphere ?
or drop a note through the web's contuct us ?

Posted: Fri Jul 08, 2005 12:26 pm

Hi,

I have exactly the same problem since a few days.
PHPed was working fine until the power suplly unit of my machine had to be changed und with that there was a BIOS reset.

Anyhow, I did some research on the web for this error message. It seems that is related somehow to DCOM and its security settings.

ddmitrie wrote:

Definitely, this message is not from PHPED.

It's a windows error message.

Maybe this information could be helpful:

Quote:

I am writing a C# program which uses COM through interop. In order to set
the security a call CoInitializeSecurity() (by DllImport). But the call
returns an error code stating 'Security must be initialized before any
interfaces are marshalled or unmarshalled. It cannot be changed once
initialized'. How can I change the COM security settings in C# ?

Carlo

---
Thomas Scheidegger [MVP] NETMaster (VIP) replied:

If there is any [STAThread] or [MTAThread] attribute
applied to your main/Main function, do REMOVE it and write:

// !no [stathread] here!
Main()
{
System.Threading.Thread.CurrentThread.ApartmentState = ApartmentState.STA;
hr = CoInitializeSecurity(...

--
Thomas Scheidegger - MVP .NET - 'NETMaster'
-

(found at )

Maybe you already have a fix for this problem?
That would be great because for now I can't really make use of PHPed - it just won't start up completely. It's just calling DBGListener which is producing the error message over and over again.
To get phped to work I have to remove/delete the "debugger" directory so it can't find it. But then it's just an editor without debugging....

Andreas

Posted: Sat Jul 09, 2005 4:32 pm

DbgListener has a clear core related to DCOM security and may not cause the problem.

jphilapy replied to me:

Quote:

I finally solved my problem. I managed to scrap all stardocks software from my pc in safe mode. Whatever they are doing is breaking applications big time. Now that it is all gone, my programs work fine.

Posted: Sun Jul 10, 2005 2:25 pm

Thank you for posting jphilapy's reply. It was really helpful because I was able to get phpED and the debugger running and up again.

Indeed the problem had nothing to do with hardware or bios changes.
I own Object Desktop from Stardock and with the latest update of some of its components the problem must have come. Mad

I was using phpED and Object Desktop for quite a while and there was no problem with that since then.

OK - after uninstalling all Stardock Software phpED (that is: the debugger) worked fine.
Then I re-installed component after component of Object Desktop (each after rebooting and testing if phpED/DBG are still working). What I didn't install was the latest version of IconX (version 1.00c[b].002). So far everything is working as it should. Seems that this IconX version is causing the problem.

Question

I can't imagine how such a piece of software could interfere with DBGListener .... Shocked

Again, thank you for this tip!

Andreas

Posted: Mon Jul 11, 2005 2:25 am

Quote:

I can't imagine how such a piece of software could interfere with DBGListener

DBGListener implements some COM classes and has its own AppID and in particular calls CoInitializeSecurity() immediately after CoInitialize(). Seems IconX makes something to COM or DCOM functionality and probably breaks it.