Setting up ACT! as a linked server
I am trying to set up ACT! as a linked server in SQL2000. I have lots of other linked servers (Sybase, Oracle)
I am using the ACT! OLE DB provider supplied with ACT.
I have registered the dll using regsrvr32
I have created a udl file that tests OK when i run a text connection.
However when I try to list tables in the linked server I get an Error 7403 - could not locate registry entry for OLE DB provider ACTOLEDB.1
help please !
I am using the ACT! OLE DB provider supplied with ACT.
I have registered the dll using regsrvr32
I have created a udl file that tests OK when i run a text connection.
However when I try to list tables in the linked server I get an Error 7403 - could not locate registry entry for OLE DB provider ACTOLEDB.1
help please !
ASKER
thanks for the feedback.
The dll has been registered on the server. ACT is installed on the same server. I am trying to set up the linked server on the SQL server (not via a workstation). Have tried both the wizard and sp_addlinkedserver.
As far as I can see you can't set up ACT using ODBC, it has to be OLEDB.
I'd prefer not to disclose the vendor.
The dll has been registered on the server. ACT is installed on the same server. I am trying to set up the linked server on the SQL server (not via a workstation). Have tried both the wizard and sp_addlinkedserver.
As far as I can see you can't set up ACT using ODBC, it has to be OLEDB.
I'd prefer not to disclose the vendor.
Please use the steps in the articles mentioned below to check if you have the
provider in place.
http://support.microsoft.com/?id=216575
http://support.microsoft.com/?id=200794
provider in place.
http://support.microsoft.com/?id=216575
http://support.microsoft.com/?id=200794
ASKER
exec xp_enum_oledb_providers confirms that the ACT provider is present as 'ACTOLEDB.1'
good,
Can you access the ACT database from the sql server box by any way (VB, VBS, etc.)
Check permissions, UID\PWD, TCP\IP port on the ACT box, etc.
if you have sql server 2000 with >=sp3
you can try to check to act connection:
OPENDATASOURCE
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_oa-oz_2be1.asp
Can you access the ACT database from the sql server box by any way (VB, VBS, etc.)
Check permissions, UID\PWD, TCP\IP port on the ACT box, etc.
if you have sql server 2000 with >=sp3
you can try to check to act connection:
OPENDATASOURCE
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_oa-oz_2be1.asp
ASKER
Permissions are OK
I have no other apps on the server the try a connection. Might try installing excel.
The only connection that I have tried that works is a MS data link file (udl) and that just gives me a connection test OK.
I've tried OPENDATASOURCE but can't get past a syntax error. I'm beginning to suspect I need to know the precise syntax for the ACT OLEDB when running sp.addlinkedserver.
I have no other apps on the server the try a connection. Might try installing excel.
The only connection that I have tried that works is a MS data link file (udl) and that just gives me a connection test OK.
I've tried OPENDATASOURCE but can't get past a syntax error. I'm beginning to suspect I need to know the precise syntax for the ACT OLEDB when running sp.addlinkedserver.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Many thanks to all for the help - I have now solved the problem.
basically it is a registry entry issue.
The registry entry that gets created by the ACT OLEDB dll has the same data ('ACTOLEDB.1' ) for both the ProgId key and the VersionIndependentProgId key.
I noticed that for the Oracle OLEDB entry, the '.1' part was absent from the VersionIndependentProgId key, so I changed the ACT VersionIndependentProgId key to read 'ACTOLEDB'.
I then set up a new linked server using sp_addlinkedserver specifying @provider=N'ACTOLEDB' and hey presto it now works.
basically it is a registry entry issue.
The registry entry that gets created by the ACT OLEDB dll has the same data ('ACTOLEDB.1' ) for both the ProgId key and the VersionIndependentProgId key.
I noticed that for the Oracle OLEDB entry, the '.1' part was absent from the VersionIndependentProgId key, so I changed the ACT VersionIndependentProgId key to read 'ACTOLEDB'.
I then set up a new linked server using sp_addlinkedserver specifying @provider=N'ACTOLEDB' and hey presto it now works.
just make sure you did it on sql server - not your PC?
Did you try to create ODBC DSN on the sql server and create the linked server by usin the DSN?
BTW: who is the Act vendor?