Hi every1,
I have created a small SMS apllication with Windows application.
Ihave used two dll called "lcgsmsms" and "Interop.excel"
But even after adding all those dll ,while building my aplication
(1)it shows ambiguous column name and after debugging ,
(2)It shows SQL server could not connect remote connections and
(3)getting error "Retrieving the COM class factory for component with CLSID {00024500-0000-0000-C000-000000000046} failed due to the following error: 80040154."
Out of which 3rd one is more complicated ,cant find wats wrong
Kindly guide me
Thanks in advance
Doubts in a SMS applicationDLL problems in a SMS application
Page 1 of 1
1 Replies - 814 Views - Last Post: 01 February 2010 - 08:37 AM
Replies To: Doubts in a SMS application
#2
Re: Doubts in a SMS application
Posted 01 February 2010 - 08:37 AM
A quick search for your error threw up this link:
http://social.msdn.m...f-27fabe59f458/
and a good bit of help:
Make sure you look in the registry of a PC on which your app works. Don't do a search, just look through the keys in HKCR\CLSID for the GUID, they are sorted alphabetically. The fact that you can't find a DLL that can be registered with regsvr32 is a strange problem. If might live in another folder, c:\windows\system32 perhaps. Look at the properties of the WinTSRRapiLib reference in your project. Also, the component may itself use another ActiveX component that requires registration. Like the VB6 runtime files for example.
Another way to debug this problem is to use the RegMon utility, available for free at www.sysinternals.com. It shows you how your app uses the registry. Run it on yours and run it on the customer's and compare the two.
http://social.msdn.m...f-27fabe59f458/
and a good bit of help:
Make sure you look in the registry of a PC on which your app works. Don't do a search, just look through the keys in HKCR\CLSID for the GUID, they are sorted alphabetically. The fact that you can't find a DLL that can be registered with regsvr32 is a strange problem. If might live in another folder, c:\windows\system32 perhaps. Look at the properties of the WinTSRRapiLib reference in your project. Also, the component may itself use another ActiveX component that requires registration. Like the VB6 runtime files for example.
Another way to debug this problem is to use the RegMon utility, available for free at www.sysinternals.com. It shows you how your app uses the registry. Run it on yours and run it on the customer's and compare the two.
Page 1 of 1
|
|

New Topic/Question
Reply




MultiQuote



|