Problem registering dmcscripting dll in Windows 64 Pro

[rtmurphy]

Hello.

I am moving my dev enviroment to Windows Pro 64, and install version 14.2 of the reference.exe Now my C* apps in visual studio 2010 complain about the scripting library not being registered. When I go to add a reference in the project, it does not show the COM scripting library. Any suggestions?

[Spoon]

Re: Problem registering dmcscripting dll in Windows 64 Pro

Try the sample .vbs code on the scripting page, can it communicate with dbpoweramp?

[rtmurphy]

Re: Problem registering dmcscripting dll in Windows 64 Pro

I ran the script (dMC-Scripting VBScripting.vbs). While it runs, none of the controls for dbpoweramp show on the 64 bit system. Also, I noticed that my post said c* (should be c*). I'm assuming that this exercise will help in determining why the COM object does not show in visual studio's COM references in the 64 bit system, but does in the 32 bit system. In general, this means that the COM object did not register. Im not sure how to upload a file, or I would send you a PDF with screen shots of each system.

[Spoon]

Re: Problem registering dmcscripting dll in Windows 64 Pro

You have installed our installer on the 64 bit Windows (rather than copy the files from old system)?

[rtmurphy]

Re: Problem registering dmcscripting dll in Windows 64 Pro

Yes. I used your installer

[Spoon]

Re: Problem registering dmcscripting dll in Windows 64 Pro

Try installing R14.4 beta (from the beta section).

[rtmurphy]

Re: Problem registering dmcscripting dll in Windows 64 Pro

Still doesnt register the COM object. Is anyone else having this problem?

[rtmurphy]

Re: Problem registering dmcscripting dll in Windows 64 Pro

No response for a week. Still doesnt register the COM object. Is anyone else having this problem?

[Spoon]

Re: Problem registering dmcscripting dll in Windows 64 Pro

Look in the dbpoweramp install folder, there should be:

dmcscripting.dll (about 530KB, if it is 380KB then you have the 32 bit dll which is incorrect).

Next open a cmd window, with administrator elevated rights, and type:

regsvr32 "fullpath and filename of dmcscripting.dll"

Look for what regsvr32 reports.

[rtmurphy]

Re: Problem registering dmcscripting dll in Windows 64 Pro

Thank you for your reply. I have tried to manually register the dll with elevated rights (it is about 530 KB). It does report that it is registered properly. The problem is that the COM interface does not register, and hence does not show under the COM tab in VS 2010, when adding a reference. If one just references the dll by browsing to it, the application returns the following error:

Retrieving the COM class factory for component with CLSID {1C2E0932-61B5-4EAB-A832-06EE6564047D} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154

This is indicative of the COM class not being registered. This works fine under the 32 bit envirnment, but does not work under Windows 7, 64

[Spoon]

Re: Problem registering dmcscripting dll in Windows 64 Pro

We develop now on 64 bit exclusively, the dll has no problems running on for us.

[mville]

Re: Problem registering dmcscripting dll in Windows 64 Pro

The problem is that the COM interface does not register, and hence does not show under the COM tab in VS 2010

I can also confirm that the dMCScripting 1.0 Type Library does not show under References/COM in Visual Studio 2008 on Window 7, 64bit.

[Spoon]

Re: Problem registering dmcscripting dll in Windows 64 Pro

Possible bug noted, will look into this for next beta update.

[Spoon]

Re: Problem registering dmcscripting dll in Windows 64 Pro

I have just tested on a fresh version of Windows 7 64 bit, installed R14.4 beta, then ran the .vbs file from the scripting page, all worked except showing the encoder settings (which we will investigate for a later release).

Also on a fresh Windows Server 2012 64 bit.

[abe]

Re: Problem registering dmcscripting dll in Windows 64 Pro

I am having this exact same problem (except this is in windows server 2008). Did anyone that was experiencing the issue ever find a solution for this? What is the recommended fix?