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!
|
|
Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 01 Mar 07 6:58 AM
|
fiogf49gjkf0d Not sure which forum to post his but it is the second time I have seen it happen.
Customer has a web interface that uses the provider and .net to read and write data.
The app works great with 6.2.4 we upgrade following the work plan and the production web connection stops working.
We have upgraded the provider on the web server and also installed the Client just to make sure.
We have a Dev machine thats works fine after the upgrade so it is something specific to the production web server.
I have verified the production web server is using .net 2 on their website. Any advised or tests that we can try would be greatly appreciated.
Thanks in advance. |
|
|
| |
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 27 Mar 07 11:23 PM
|
fiogf49gjkf0d Well, I am not sure whether it's 7.0.1 or something else. I have my asp.net 2.0 working fine where I had SLX ole db provider 7.0 installed and then service pack 1 applied. But when I tried to move to a diferent server I installed new SLX provider 7.0.1 (.msi file as of January 2007) with no service packs and I cannot open SLX connection on that web server. Connection string is the same and I get unhandled error:
Error Message:
No error message available, result code: E_UNEXPECTED(0x8000FFFF).
Source:
System.Data
Stack Trace:
at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection) at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.OleDb.OleDbConnection.Open() at TestASPNet2._Default.Page_Load(Object sender, EventArgs e)
Any idea? Thanks much! |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 28 Mar 07 12:14 AM
|
fiogf49gjkf0d Forgot to mention: the failure occurres on Windows 2003 server [as opposed to old Windows 2000 server ] with ASP.NET 2.0.
I even installed SLX Client there and am able to successfully run SLX application and make data modifications there.
|
|
|
| |
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 28 Mar 07 1:02 PM
|
fiogf49gjkf0d Thank you Carla,
I've almost everything that you suggested except adding SLXProviderExtensions.dll (I don't think we need it since we are not using .NET extensions. It's regular ASP.NET app)
We even tried to add our slx admin account (the service account that we've created) to different settings under Local Security policies.
In IIS Applciation pool we made sure that it's running under NETWORK SERVICE.
No luck at all... |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 28 Mar 07 1:07 PM
|
fiogf49gjkf0d Lana,
I do not believe that file is optional, I could be wrong, AND it wouldn't be the first time; but I don't think I am. One thing I am sure of; the service is actually programmed to go to that file. If you run perfmon while you perform, you will see either a path not found or file not found without that folder structure and file. Oh, and you may also see an access denied if the file permissions are not granted.
c |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 16 Jul 07 3:06 PM
|
Carla,
I have a customer encountering a similar problem (they're seeing errors from the framework they're using on top of the .NET and the OLEDB provider and want to point them to your solution, but I have a question about it.
Step 1 says
Originally posted by Carla Tillman
1.) There is a defect between 7.01 and SQL2005 - so if you are using 2005; you need to change your datalink back to SQL ole (I have reported it, don't know if it is assigned a defect number yet)
|
|
What would the data link be pointed to if it's not the Microsoft OLE DB provider for SQL Server?
I'm probably missing the obvious, but it's my first day back from vacation. 
Thanks,
Jeff
|
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 16 Jul 07 3:30 PM
|
Hi ya Jeff!
Hope all is going well with you. As you had to stop vacation to start working I would assume not - vacation is better... 
When you first create the DataLink in the Connection Manager Tool, you have two choices as to what you are going to base your DataLink on (Provider Tab) ; SQL Native Client or SQLOLE. I found that if I chose SQL2005 Native Client, my external sites failed. When I swapped the DataLink to SQLOLE - they magically could make connections again. Is that the info you are looking for or did I miss?
c |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 23 Oct 07 1:07 AM
|
Hey Guys,
I thought i'd try and add some information for you on this in case it helps identify the issue. I'm a customer who wants to use the 7.0.1 SLX provider with .net 2.0 and SQL 2005 on Windows Server 2003. On my local development machine I used exactly that configuration aside from being on XP SP2 rather than Windows 2003, and the SLX provider works just fine, however when I deploy the code to the development server I get exactly the same error described above.
i.e. "No error message available, result code: E_UNEXPECTED(0x8000FFFF)." - Just as the connection is trying to be opened.
If anyone has had a successful resolution to this problem I'd love to hear how!
Cheers! |
|
|
| |
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 23 Oct 07 9:52 PM
|
Hey Carla,
Yep the development server is in the same domain, and there is no firewalls running on either the development server or the main sales logix server. I have logged onto the development server as an admin and used the "run as" facility for Internet Explorer to run as my standard user to test if there was any "double-hop" authentication issues, but whether i run remotely or locally I still get the same error.
I'm thinking more and more that this is really something relating to the differences between Windows Server 2003 and XP SP2. Blatantly different underlying assemblies which are trying to be used its just determining which assemblies are perhaps causing the issue, I will run a filemon analysis between the two machines shortly as see if that shows anything up.
Matt |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 16 Nov 07 3:54 PM
|
| Anyone found any solutions on this? I have a couple of webservice sites on win 2k3 trying to connect to the app server via the provider, i have done all the steps decribed above and i still get the e_unexpected. Every new environment i deploy the sites to this happens i work on it for 4 hours and reboot the server umteen times and then all the sudden it starts working. When i talk to SAGE they refuse to give support since it is a custom application. |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 16 Nov 07 6:17 PM
|
In general, this is a permissions issue.
- Install SLXSystem.exe to run as a Service and make sure that the account you give it has the necessary permissions to access the Network and DB resources.
- Make sure that the Site is run with the necessary permissions to access DB and Network resources.
The problem followed somewhat this path:
- SLX System is loaded while you are logged on, and remains loaded. It loads with your credentials so it works fine.
- Eventually SLX System unloaded.
- SLX System is reloaded when new requests come in, but without the appropriate access.
By setting it up as a Service you prevent it from being unloaded and you force the credentials on it.
|
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 08 Apr 08 4:45 AM
|
My system uses sql2000,vs2003, Saleslogix 7.2, has the same problem as lana.
connection code:
string constr= "Provider=SLXOLEDB.1; Password=\"anyuecrm\"; Persist Security Info=True;User ID=admin;Initial Catalog=anyue4-1;Data Source=ck2602;Extended Properties=\"PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;SVRCERT=;\"";
System.Data.OleDb.OleDbConnection o_con = new OleDbConnection(constr);
o_con.Open();
Error Message:
No error message available, result code: E_UNEXPECTED(0x8000FFFF).
Stack Trace
at System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr)
at System.Data.OleDb.OleDbConnection.InitializeProvider()
at System.Data.OleDb.OleDbConnection.Open()
at Legris.Form1.button2_Click(Object sender, EventArgs e) in d:\tracy\legris\form1.cs:line 189
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
what should i do with that?Thanks |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 08 Apr 08 10:52 AM
|
Is anyone switching from a 32-bit to a 64-bit OS on the production end? Also, how is .NET getting installed? I don't believe 2.0 comes standard in 2003. Are you using the SalesLogix install to put .net on in both places? Has either upgraded to .net 2.0 sp1? There *is* a 64 bit .NET framework and sometimes the ASP.NET IIS process will "link" to that version, which I believe can cause issues with non-32 bit processes. What about MDAC versions? Are they the same on both machines?
The .NET extensions gets installed and registered into the GAC (global assembly cache) at the end of every SalesLogix client install I believe. It's those flurry of dos boxes that pop up. I'm not exactly sure if this happens on the web client side becuase it's been so long since I put it on our dev machine. |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 08 Apr 08 1:03 PM
|
We ran into the same issue, a web service on a Windows Server 2003 server accessing a SalesLogix v7.0.1 database using SQL 2005 SP1.
We finally have a connection working when we added the NT AUTHORITY\NETWORK SERVICE (S-1-5-20) user to the Administrators group on the web server. The question is, how much of a security risk is this?
|
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 09 Apr 08 1:09 AM
|
As all of us agree, this is a security setting.
My finding is that if you setup the SLXSystem to run as a Service, and then change its credentials to Network Service (or to a Service Accounts with enough Permissions) the problem goes away.
The issue we were running into was that once Slxsystem exited, next time it loaded it didn't have the proper permissions, so setting it up as a Service and granting it the appropriate permissions made it more stable (as a service) and gave us predictible permissions.
|
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 28 Apr 08 1:20 PM
|
Thanks to everyone who contributed to this thread. So far this thread has provided WAY more information than I've been able to get from Sage - and Carla's first post of this problem is over a year old!!!
However, despite doing everything described herein, I'm still not working.... 
Filemon traces are telling me that the SLXProviderExtensions.dll are to blame and I'm pretty convinced the solution to this problem lies with this driver. If/When I figure this out, I'll post my solution in case it was different from everything else above so far.
Meawhile - can anyone provide any rational for why this driver is where it is? I've tried moving & registering it to C:\pf\slx\ (duh!) but filemon still has it looking in the \default user\ profile... And even when it's there I'm getting Name Collision/Access Denied/Path Not Found even though I've granted rights to those structures to everyone. I've also seen where it gets copied down to every users profile who is logged into that machine (Citrix) and has launched anything SLX - even though my webservice keeps looking for it in Default User. 
Sage's last suggestion was to make my service account a Domain Admin. Anyone else here have a IT security department stupid enought to let you do such a thing? 
I'm tempted to skip the provider all together and go straight to the database... |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 29 Apr 08 3:47 PM
|
Well, immediately after I successfully got my webservice to work end to end on my dev box using SQL directly (instead of the Provider), I went back to document more of this problem for Sage and saw something in the Filemon traces I’d missed the first 3 dozen or so times…
w3wp.exe is the process getting the name collision/access denied in the Default User profile folder structure. (By default this is normally the IWAM_machine account). In our case, we have predefined service accounts running these application pools (different from the service account named and running SalesLogix Service).
I granted these service accounts full file privledges to ‘C:\Documents and Settings\Default User\’ and everything started working.
I even went back and removed some of the other changes I had made in testing. I’ve listed the minimum steps below (and I haven’t confirmed that all of these are necessary either, but they’re how I’m going to Prod with this so it is how it is):
If you installed the provider/admin tools/client etc while logged in as something other than the service account that runs the provider, uninstall it all. Clean up the reg (HKCU & HKLM), and C:\Program Files. Reinstall it all while logged in under the same credentials that run your provider service. (Not entirely sure this is necessary, but I don’t want to uninstall/reinstall again to test – sorry. At minimum, make sure your Service Account has Admin rights to that machine – it would have needed them to do the installs anyway.)
Modified SalesLogix System to run as a service, running it under the same credintials as SalesLogix Server. Although it’s probably no longer necessary, I also added the shutdowndelay reg entry (set to 0) as well. (As with the prior step, I’m not sure this is necessary either.)
My webservice was running in an application pool – in this case the account running the pool needs full file permissions to ‘C:\Documents and Settings\Default User\’. (This would be IWAM by default.) If you are not in a pool, then perhaps it is just the IUSR account as Carla mentions above. This is the most critical step. For whatever reason, SLX needs to write (and rewrite) the SLXProviderExtensions.dll into this structure and run it from there. 
Things I did NOT do (actually, I did do some of them, but later removed them when they proved not necessary):
Add Service Account to 'Distributed Com Users' group (added and later removed this with effect).
Change IUSR account on website to Service account (I went back to meek IUSR account here with no issues).
Add Service account to ‘Act as part of the operating system’ policy (again, removed to no effect).
Make service account domain admin (I couldn’t bear the thought of the ridicule that would surely have been heaped – and deserved – upon me had I made this request to our security department so I never asked. As it turns out, this would not have worked anyway in my case as it was the application pool accounts that needed the elevated rights – and then ONLY to the default user profile).
I strongly suspect that the rights to the profile structure are all that is really necessary here. I usually dread resorting to filemon/regmon traces, but in this case I wish I'd have run them earlier. I <3 sysinternals. |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 06 May 09 4:04 PM
|
Hello Shawn,
It's been a long time since I posted my issue with the Error: Unable to initialize data dictionary. source: SalesLogix OLE DB Provider.
We've upgraded to 7.2.2 recently but I doubt this is causing the problem. My external ASP2.0.net app is trying to write into the SLX database by utilizing SLX Ole DB provider. The SLXSystem is running as a service under domain account which is admin on that server box.
It seems that application is working for an hour or so and then suddenly stop working... Could be that it stops writing to a database due to some collision when multiple users are trying to use it.
The only thing that helps is rebooting the server....
I did granted full access permissions for both IWAM_ and IUSR_ accounts to the C:\Documents and Settings\Default User and the user that is admin on this machine...
Also, how does SLX Provider handle connection pooling? What is the default there?
Any help is appreciated...
Thanks!
Lana |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 06 May 09 6:55 PM
|
Hi Lana,
Glad to hear you guys still around (and now running 7.2.2).
Questions regarding your App?
- Is the Application pool set to reset when idle?
- Also, is it possible that the SLXSystem is crashing and then a new instance is restarted by IIS? In other words, when it freezes, do you see only one instace of SLXSystem and is it running with the correct credentials?
- Instead of rebooting, if you just Stop IIS, Restart the SLX System and then Restart IIS, does the application becomes functional again?
==> What credentials are you using for your Site and your Application pool? I would suggest you make it the same as the one that you are using for the SLXSystem service.
I have run into this type of issues when my IIS instances are running under the ASPNET account. The app works for a while, but then it stops working and requires a bit of effort to shut everything down on the correct order and get it to reinitialize before being able to restore functionality.
Best regards,
Raul |
|
|
|
Re: Problems with OLEDB provider and website after upgrade to 7.0.1
Posted: 06 May 09 11:25 PM
|
Hi Raul! I just knew you would be the first one to respond.
Ok... It happened again about 1.5 hours ago. The user was working quite late so I think she was the only one accessing application.
To answer your questions:
--The Recycling is on in Application pool.
--Don't think that SLXSystem is crashing (it's our secondary sync server machine...) and there is just one instance of it running always
-- I tried different ways/order/sequence of Stopping/Restarting IIS and/or SLX System with no success
but....
Thank you for your suggestion to check credentials on Application Pool.
Web site was running as IUSR and Application Pool was configured under Network Service
I changed it to IWAM (it was grayed out with the password already there...), restarted IIS, restarted SLX System, restarted IIS again and .... magically it worked... Not sure for how long though...
I wouldn't want to change IIS and Application Pool Identity to slxadmin (admin account under which SLX System is running) since if it comes to reconfiguring IIS to IUSR or IWAM - I don't know passwords for these accounts.
Again,
Thanks for your help!
Best,
Lana |
|
|
| |
| |
| |
|