Simplewire ActiveX COM object for sending/receiving SMS

Hi all,

Like many, I have a ActiveX COM object that works fine locally but not on DASP.net. It's purpose is to send and recieve XML messages to a SMS gateway which then communicates with mobile phones.

I've read a few threads about how to solve the issues I'm having:

Retrieving the COM class factory for component with CLSID {67D6D52C-6306-4A02-BA60-19B2293DF5E0} failed due to the following error: 80040154.



The .dll is in my \bin directory and I have changed the target platform in my build properties to "x86" from "AnyPC" but this didn't solve it. I've seen a few posts on changing permissions on folders, but nothing that made sense to me. Also seen a few from Bruce where he asks to see web.config file, but never saw how those were resolved.

Can anyone help? This is critical to my app, and if it can't be supported I'll have to find another hosting provider.

Thanks,

-Mike.

 

Is this component included on the DASP platform supported component list? If not it simply won't work because COM components need to be registered on the server operating system and DiscountASP.NET have strict policies in place (for good reason) that prevent 'special request' COM component being registered on the server.

 

Can you point me to the list?

Simplewire (Openmarket) is one of maybe 4 big SMS gateways in the world. It's not some little fly-by-night company.

 

This is the official list on the public website: http://www.discountasp.net/features.aspx#components

I don't doubt you, but it's DASP that you'll have to convince on that one

 

Just as a side thought on this - doesn't this sms gateway provider support a .NET / HTML / WS interface? Providing only a COM component for system integration does seem to be a limitation given current technology.

 

When a user approaches us to register a component on the servers, we take a few things into account, and one of those things is demand. We keep track of all feature requests, and if the demand is sufficient, we will add the feature or component, make changes to configuration, what have you. In this case, I'm afraid that the demand for an SMS gateway is just not there.

Our server management procedure requires that all components that are added are thoroughly tested and constantly maintained. For that reason we do not register a specific component on one server - it has to be registered on all servers - and as I'm sure you can understand, that is why user demand is an important factor.

 

Understood.

I read a little further and was wondering if any of these would help:

My app is built in .NET 2.0. If I were to build in 3.5, would that solve the "trust" issue?
Another idea - from the Simplewire SDK description:

"The ActiveX SMS SDK provides easy, high-level control of the Simplewire wireless text-messaging platform. Designed be to be as developer-friendly as possible by hiding the intricacies of the XML format required to communicate with the Simplewire WMP (Wireless Message Protocol) servers, The ActiveX SMS SDK makes it possible to send an SMS message off with as little as two lines of code. The 32-bit ActiveX SMS SDK is implemented as a COM object (DLL). As an ATL object, the ActiveX SMS SDK does not require the Microsoft Foundation Class DLLs to run. This allows your projects to require less memory, to run faster, and to have a reduced footprint. ASP applications will execute quickly, installation packages will be smaller, and less dependency issues will arise for your end-users. "

Does this mean I can include/reference this ATL object (swsms.tlb) in my ASP.NET solution rather than the Interop.Simplewire.dll (which I'm using now) and that might solve the problem?

 

As I read that it still requires registration of the component ("ActiveX SMS SDK is implemented as a COM object").