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!
|
|
IIS and SLX Ole DB Provider
Posted: 29 Apr 09 10:38 AM
|
Hi all,
I have the joy of working blindly with two development groups on an Extranet project.
One group built the interface. A second group built a web service used by the interface to get data. The group that built the web service does not know anything about the SLX database. I was charged with building an assembly to do all SLX database functions and return results.
I built my assembly in VS 2005 C#. Built a test exe to access and call functions in the dll. Everything works fine.
The Web Service was built in VS 2008 C#. When the web service calls my dll, the connection to the SLX database fails with the message 'Unable to initialize data dictionary'.
I built and tested the dll on the same test server the web service in running on.
Why would the dll fail to connect to the SLX database when called from the web service but work fine when called from my test exe on the same machine?
Anyone have any ideas?
Thanks
|
|
|
|
Re: IIS and SLX Ole DB Provider
Posted: 29 Apr 09 12:31 PM
|
Update:
I have isolated the problem to the SLX Data Provider.
I rebuilt my dll to make a connection to the SLX database directly through SQL and it will connect using the web service.
I need to connect via the SLX Data Provider.
Now the problem is why wont the SLX Data Provider allow the connection when called from the web service?
|
|
|
|
Re: IIS and SLX Ole DB Provider
Posted: 29 Apr 09 2:13 PM
|
Have you tried a test .udl file on the server where the webservice resides? Can you connect? I suspect you need to install the SQL Native Client.
Timmus |
|
|
|
Re: IIS and SLX Ole DB Provider
Posted: 29 Apr 09 2:51 PM
|
The test server the webservice resides has the SalesLogix database (SQL 2005 Express) and both the saleslogix server and lan client.
SQL Native Client is in installed.
I did try a test .udl from the directory where the dll lives, using the SalesLogix OLE DB Provider.
the Test Connection said Successful.
I can move the .dll to almost any other location on the machine, change the reference to the .dll in my test app to those locations and everything works fine. I move the .dll to the directory where the webservice lives and the connection fails.
as well as .Net Extension assemblies th
I have built other .exe's that use the exact same connection string to access the databse and all work fine.
I have built numerous .Net Extensions incorporated into SalesLogix, again with the same or similar connection strings and they all work fine.
Just this new webservice is giving me fits.
Jeff
|
|
|
|
Re: IIS and SLX Ole DB Provider
Posted: 30 Apr 09 6:40 AM
|
Jeff when you are testing with your Exe you are using your local credentials and have full access to the underlying file system. When you are testing on IIS you are using the user associated with your IIS process. The provider needs access to certian directories I believe that the IIS user does not have access to. When we set up the web we create a 'Special' web dll user that the App Pool runs under. Have you tried to walk through the steps of creating the WebDll user and assigning it to the app pool for your web service?
Kindest,
Mark |
|
|
|