After installing XE3 on win 2008 server, a confirm box pops up:

Exception EPackageRegistrationException in module coreide170.bpl at 00034c8B. Registration procedure, DotNetReg.IDERegister in package c:\program files(x86)\embarcadero\rad studio\10.0\Bin\dotnetcoreide170.bpl raised exception class EOleSysError: Class not registered AssemblyName: Borland.Studio.Interop.dll.

I've installed xe3 several times and have never seen this before. Any ideas?

TIA,

CKD

Charles wrote:

> Exception EPackageRegistrationException in module coreide170.bpl at
> 00034c8B. Registration procedure, DotNetReg.IDERegister in package
> c:\program files(x86)\embarcadero\rad
> studio\10.0\Bin\dotnetcoreide170.bpl raised exception class
> EOleSysError: Class not registered AssemblyName:
> Borland.Studio.Interop.dll.

Sounds like Borland.Studio.Interop.dll has not been registered with COM/DotNet 
prior to dotnetcoreide170.bpl being loaded.

-- 
Remy Lebeau (TeamB)

> {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> Charles wrote:
> 
> > Exception EPackageRegistrationException in module coreide170.bpl at
> > 00034c8B. Registration procedure, DotNetReg.IDERegister in package
> > c:\program files(x86)\embarcadero\rad
> > studio\10.0\Bin\dotnetcoreide170.bpl raised exception class
> > EOleSysError: Class not registered AssemblyName:
> > Borland.Studio.Interop.dll.
> 
> Sounds like Borland.Studio.Interop.dll has not been registered with COM/DotNet 
> prior to dotnetcoreide170.bpl being loaded.
> 
> -- 
> Remy Lebeau (TeamB)

It does indeed sound like that. Any idea how to overcome the problem?

> {quote:title=Charles Dupont wrote:}{quote}
> > {quote:title=Remy Lebeau (TeamB) wrote:}{quote}
> > Charles wrote:
> > 
> > > Exception EPackageRegistrationException in module coreide170.bpl at
> > > 00034c8B. Registration procedure, DotNetReg.IDERegister in package
> > > c:\program files(x86)\embarcadero\rad
> > > studio\10.0\Bin\dotnetcoreide170.bpl raised exception class
> > > EOleSysError: Class not registered AssemblyName:
> > > Borland.Studio.Interop.dll.
> > 
> > Sounds like Borland.Studio.Interop.dll has not been registered with COM/DotNet 
> > prior to dotnetcoreide170.bpl being loaded.
> > 
> > -- 
> > Remy Lebeau (TeamB)
> 
> It does indeed sound like that. Any idea how to overcome the problem?

The solution:

http://blogs.msdn.com/b/vijaysk/archive/2009/08/16/you-must-use-the-role-management-tool-to-install-or-configure-microsoft-net-framework-3-5.aspx