32 bit DLL in SQL Server 2005 64 bit

Hello,
I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
Server 2005 64 bit edition.
The same extended stored procedures now give error when I call them using
sp_OACreate.. It gives the error "Class not registered" even though the DLL
file is present in the "SysWow64" folder and it has been correctly registere
d
using regsvr32.
On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
right?. What options do I have now so that I can continue the use the same 3
2
bit DLLs in 64 bit SQl Server 2005?.
Thanks for any help!
GaneshHi Ganesh
I am not an expert on this but it looks like only 64 but registrations can
be used by sp_OA... but I have not found anything to say that is the case.
John
"Ganesh Muthuvelu" wrote:

> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedur
es
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to S
QL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DL
L
> file is present in the "SysWow64" folder and it has been correctly registe
red
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same
32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganesh|||For a 64 bit installation, you need 64 bits dll's.
You cannot mix 64 and 32 bit code in one process, that's why you cannot
use 32 bits dll's in a 64 bit process (or vice versa).
Ganesh Muthuvelu wrote:
> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedur
es
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to S
QL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DL
L
> file is present in the "SysWow64" folder and it has been correctly registe
red
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same
32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganesh

32 bit DLL in SQL Server 2005 64 bit

Hello,
I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
Server 2005 64 bit edition.
The same extended stored procedures now give error when I call them using
sp_OACreate.. It gives the error "Class not registered" even though the DLL
file is present in the "SysWow64" folder and it has been correctly registered
using regsvr32.
On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
right?. What options do I have now so that I can continue the use the same 32
bit DLLs in 64 bit SQl Server 2005?.
Thanks for any help!
Ganesh
Hi Ganesh
I am not an expert on this but it looks like only 64 but registrations can
be used by sp_OA... but I have not found anything to say that is the case.
John
"Ganesh Muthuvelu" wrote:

> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DLL
> file is present in the "SysWow64" folder and it has been correctly registered
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same 32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganesh

32 bit DLL in SQL Server 2005 64 bit

Hello,
I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
Server 2005 64 bit edition.
The same extended stored procedures now give error when I call them using
sp_OACreate.. It gives the error "Class not registered" even though the DLL
file is present in the "SysWow64" folder and it has been correctly registered
using regsvr32.
On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
right?. What options do I have now so that I can continue the use the same 32
bit DLLs in 64 bit SQl Server 2005?.
Thanks for any help!
GaneshHi Ganesh
I am not an expert on this but it looks like only 64 but registrations can
be used by sp_OA... but I have not found anything to say that is the case.
John
"Ganesh Muthuvelu" wrote:
> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DLL
> file is present in the "SysWow64" folder and it has been correctly registered
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same 32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganesh|||For a 64 bit installation, you need 64 bits dll's.
You cannot mix 64 and 32 bit code in one process, that's why you cannot
use 32 bits dll's in a 64 bit process (or vice versa).
Ganesh Muthuvelu wrote:
> Hello,
> I have been using a 32 bit DLL in SQL Server 2000 extended stored procedures
> and it works just fine. Now I have upgraded my SQL Server 2000 32 bit to SQL
> Server 2005 64 bit edition.
> The same extended stored procedures now give error when I call them using
> sp_OACreate.. It gives the error "Class not registered" even though the DLL
> file is present in the "SysWow64" folder and it has been correctly registered
> using regsvr32.
> On a SQL Server 2005 32 bit edition, it works well. So, it is just the SQL
> Server 2005 64 bit edition that seems cannot load the 32 bit DLL.. Is that
> right?. What options do I have now so that I can continue the use the same 32
> bit DLLs in 64 bit SQl Server 2005?.
> Thanks for any help!
> Ganeshsql

20536: Unable to logon server

I have VB 6.0 Application calling Crystal Report 7.0 based on SQL Server 2000 datbase.

I use the LogonServer method with parameter p2ssql.dll to make the database connection.

I have used the above method for my Crystal Report for last 6 years and worked fine until now but now I get the "20536: Unable to logon server " in few XP OS machines.

This again works in the test XP machine I have used, I have almost tried all things I can try to fix the problem.

Does anyone have similar problems and if so how they dealt with it.

Any help in this regard is highly appreciated.

ThanksHigher security levels in XP, at a guess.
Do you have subreports??
If so, you may find that before your OS was allowing subreports to use login info from parent report, but now is breaking because OS demands you supply login info for each subreport.
In which case. iterate thru subreports collection and supply same login info to each subreport.

dave

2005:how to find installed assemblies

Did this as a exercise and am fed up with my fruitless searching.

Went and create an CLR assembly and all with min hassel. Now that I
have that dll out there, I am tring to find some system table or some
display in management studio that shows me where the file is located on
the hard drive and cannot locate it.

Can someone please point me in the correct location.

Thanks.LLik (wdieteri@.rmi.net) writes:
> Did this as a exercise and am fed up with my fruitless searching.
> Went and create an CLR assembly and all with min hassel. Now that I
> have that dll out there, I am tring to find some system table or some
> display in management studio that shows me where the file is located on
> the hard drive and cannot locate it.
>
> Can someone please point me in the correct location.

Use this link in Books Online:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/tsqlref9/html/b2e71480-92b2-4610-a4ff-dafb121087d9.htm

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

2005 using CLR for UDF accessing DirectoryServices

Not sure if this is correct group, but I cannot access
DirectoryServices namespace (directoryservices.dll) when creating (or
running) a C# UDF.
It seems that this is a 'feature', but why - and is there a way round
it - I need to access Active Directory from the UDF.
Thanks
Howard.Generally your assembly needs 'EXTERNAL_ACCESS' or 'UNSAFE' permission set.
What error message is generated?
WBR, Evergray
--
Words mean nothing...
"HowardB" <howard.birkett@.collercapital.com> wrote in message
news:1140603708.038477.288580@.g14g2000cwa.googlegroups.com...
> Not sure if this is correct group, but I cannot access
> DirectoryServices namespace (directoryservices.dll) when creating (or
> running) a C# UDF.
> It seems that this is a 'feature', but why - and is there a way round
> it - I need to access Active Directory from the UDF.
> Thanks
> Howard.
>|||Thanks Evergray, got a response from an MVP in the dotnet.framework
group. Seems that I first have to add DirecroryServices to sql with
CREATE ASSEMBLY with unsafe permission set after turning on the
database TRUSTWORTHY - then, yes, I can add my assembly with UNSAFE
permission set- haven't tried it yet!!
H