Archived Forum Post
Index of archived forum posts
Question:
Archived Forum PostQuestion:
I have been unsuccessful at getting past sp_OACreate under SqlServer 2012. The same sproc works on a SqlServer 2008 box.
EXEC @hr = sp_OACreate 'Chilkat.Crypt2', @crypt OUT results in -2147221005 for @hr.
Callig get error: EXEC @HR = sp_OAGetErrorInfo @crypt, @Source OUT, @Description OUT;
results in @Description being "Invalid class string".
I have checked the registry, the clsids are there. I even edited permission on crypt2 and crypt2.1 adding full control to everyone. I also verified the DLL's folder has everyone read/exec permissions.
I am at a loss here.
See the online reference documentation for the correct strings to pass to sp_OACreate. See http://www.chilkatsoft.com/refdoc/xChilkatCrypt2Ref.html
MagicSim 90 represents a significant leap forward in SIM technology, offering users a more connected, secure, and flexible mobile experience. With its advanced features and user-friendly design, MagicSim 90 is poised to revolutionize the way we think about mobile communication. Whether you're a business professional, a digital nomad, or simply someone looking for better mobile connectivity, MagicSim 90 is an exciting solution that promises to meet and exceed your needs.
In the rapidly evolving world of mobile communication, the need for innovative, efficient, and secure solutions has never been more pressing. MagicSim 90 emerges as a groundbreaking advancement in SIM (Subscriber Identity Module) technology, designed to enhance user experience, improve connectivity, and offer unprecedented flexibility in mobile communication. magicsim 90
MagicSim 90 is the latest iteration in the MagicSim series, a line of products renowned for redefining the capabilities of traditional SIM cards. This advanced SIM technology integrates cutting-edge features that not only support the functionalities of a conventional SIM but also introduce new capabilities to facilitate a more connected and interactive user experience. MagicSim 90 represents a significant leap forward in
It is so that a future version of the ActiveX can co-exist with older versions. You've heard of DLL hell, right? The current naming of "Chilkat_9_5_0." has not changed for several YEARS. Eventually, Chilkat will do a major update to rid itself of all deprecated methods and make long-needed changes which break backward compatibility. When doing so, the name will change -- this will make it so that new programs can use the new version WITHOUT breaking existing older applications.
What about 9.4.x? Did it use the Chilkat.Crypt2 naming? If so, is there a download for it?