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
You cannot jump straight to verification. First, go to the forum’s homepage and complete the standard registration form. Use a legitimate email address—not a temporary one (e.g., from 10minutemail). The forum automatically blocks disposable email domains.
Before diving into the verification process, it is crucial to understand the foundation of the community. Andipinkandilandforum is a specialized discussion board (a "forum" in the classic sense) that blends elements of fandom, support networks, and digital content sharing. While its exact focus has evolved over time, the forum is widely recognized for its curated approach to user-generated content, strict moderation policies, and a culture that values authenticity over anonymity. andipinkandilandforum verified
: A verification badge next to a username immediately establishes authority and reliability within the thread, making their advice or posts carry more weight. Other Common Verified Features: You cannot jump straight to verification
Since "andipinkandilandforum" appears to be related to niche online communities or content repacks The forum automatically blocks disposable email domains
: Verified members often gain entry to exclusive threads or private sections.
This status allowed for:
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?