11/26/2024 6:25:50 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
SLXOLEDB On W2K3 x64 edition
Posted: 06 Jun 07 12:13 PM
|
| We are trying to install SLX 6.2 on a 64 bit server running SQL2K5 enterprise edition. The SalesLogix Server installs fine and the install for the OLE provider also installs fine. However, we get a "Provider is no longer available. Ensure that the provider is installed correctly" error when trying to test it with a .udl file. I need the provider on the server because I've got Integration services packages inserting data and I use various procedures within it (namely DBIDs). I was wondering if anyone else has run into this problem or a similar one and if it's possible to get it to work on this configuration. Any help would be great! Thanks. |
|
|
|
Re: SLXOLEDB On W2K3 x64 edition
Posted: 07 Jun 07 9:38 AM
|
I don't know if this is it, exactly, but SalesLogix does not support 64 bit. I tried installing 7.01 on a 64 bit server, and I ran into a few problems. I imagine an even earlier version of SalesLogix is less able to handle 64 bit. However, rather than telling you that you are screwed, I'll try with a couple of recommendations:
- Did you use the Native Client for the SQL Server connection and not the SQL Server OLEDB Provider? That little issue has caused me headaches in the past.
- Are you coding the integration with the integration services? If so, you may be able to access the provider on the SalesLogix server instead of the provider on the 64 bit server by programming the connection using ADO. Doing it this way can help you completely avoid having any piece of SalesLogix on your server. You can create SalesLogix IDs doing it this way as well, by accessing the SalesLogix virtual stored procedure, slx_DBIDs. More information on using this can be found in the LAN Developers Reference under SalesLogix Stored Procedures found on the SalesLogix support site. |
|
|
|
Re: SLXOLEDB On W2K3 x64 edition
Posted: 07 Jun 07 1:14 PM
|
| Thanks for the quick reply Jeff. I tried both the Native client and the sql oledb provider and I got the same thing. Initially, we were going to have the SalesLogix Server and the DB server be one in the same. However, after messing around with this thing all day yesterday I finally convinced my boss to do the same thing you recommended and build a 32-bit w2k3 VM and have it host the SalesLogix Server so that its separate from the DB server. This was the way I wanted to do it originally as I was trying to avoid installing anything other than SQL2K5 on my the DB server. Once I did that everything was peachy! Thanks again! |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|