Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Tuesday, May 14, 2024 
 
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!
 External Development Forums - SalesLogix OLEDB Provider
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.
Forums RSS Feed


 Back to Forum List | Back to SalesLogix OLEDB Provider | New ThreadView:  Search:  
 Author  Thread: Our SLXDBEngine.DLL keeps crashing
Shane
Posts: 38
 
Our SLXDBEngine.DLL keeps crashingYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 12 Jun 08 12:47 PM
here's the error message
szAppName : w3wp.exe szAppVer : 6.0.3790.3959
szModName : SLXDBEngine.DLL szModVer : 7.2.1.1672 offset : 0006a46f

The only other hint I have in the event viewer is that on our custom tables we keep getting this error

Procedure DoLog. Error:LogParamSQL: OLEDBValueToVariant
Unsupported DBType: 7
SQL: insert into .......


It keeps causing the SLXDBEngine to crash
which causes our whole website to crash
and thus we have to reset the server

And of course it only happens on production
We can't even get any of these error message to show up on our staging environments

Is there anything else I can do to inspect or possibly figure out why this is happening?
Thank you in advance
[Reply][Quote]
Mike Spragg
Posts: 1226
Top 10 forum poster: 1226 posts
 
Re: Our SLXDBEngine.DLL keeps crashingYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 13 Jun 08 3:12 AM
Do you use remotes as well ? If so, grab a ton of TEF files and examine them.
As these are custom tables I would suspect custom code to be the issue - and the log above backs that up - OLEDBValueToVariant. The fact you are also using direct SQL injection (insert into) is further evidence of this. So, I suspect you - not the product
[Reply][Quote]
Shane
Posts: 38
 
Re: Our SLXDBEngine.DLL keeps crashingYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 22 Jul 08 1:58 AM
haha yea I doubted that it was the product.

I figured it out here
http://www.slxdeveloper.com/forum.aspx?forumid=3000&postid=17628

and on a side note
is there something else I should be using to insert records into SLX besides Direct Sql injection through the OLEDB Provider?
[Reply][Quote]
Mike Spragg
Posts: 1226
Top 10 forum poster: 1226 posts
 
Re: Our SLXDBEngine.DLL keeps crashingYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 23 Jul 08 2:58 AM
Yes, you can use the "select cols from table where 1=0" approach.
You can then use :

Dim objSLXDB, objRS, strSQL

If IsEmpty(objSLXDB) Then
Set objSLXDB = New SLX_DB
End If

Set objRS = objSLXDB.GetNewRecordSet
strSQL = "Select * from myTable where 1=0"

objRS.Open strSQL, objSLXDB.Connection
objRS.AddNew

With objRS
.Fields("CONTACTID").Value = ConID
.Fields("CREATEUSER").Value = Application.BasicFunctions.CurrentUserID
.Fields("MODIFYUSER").Value = Application.BasicFunctions.CurrentUserID
.Fields("CREATEDATE").Value = Now
.Fields("MODIFYDATE").Value = Now
.Fields("Q1").Value = "F"
.Fields("Q2A1").Value = "0"
.Fields("Q2A2").Value = "0"
.Fields("Q2A3").Value = "0"
.Fields("Q2A4").Value = "0"
.Fields("Q2A5").Value = "0"
.Fields("Q2A6").Value = "0"
.Fields("Q2A7").Value = "0"
.Fields("Q2A8").Value = "0"
.Fields("Q3A1").Value = "F"
.Fields("Q3A2").Value = "F"
.Update
If ErrorCheck (Application.Translator.Localize("Error updating...")) > 0 Then exit sub
.Close
End With

Set objRS = Nothing

This makes the code easier to read - and you don't have to worry {too much} about data types.
Mike
[Reply][Quote]
Shane
Posts: 38
 
Re: Our SLXDBEngine.DLL keeps crashingYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 23 Jul 08 3:10 AM
Oh ok that's what you meant

Yea that would have resolved my datatype issue

But we're actually not generating any SQL ourselves
that was just the error message cataloged by the events viewer in windows

We're using an ORM to do all the nasty SQL stuff
and sometimes it means having to fix nuances here and there
but overall it works out super

thanks for the reply
[Reply][Quote]
 Page 1 of 1 
  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!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 5/14/2024 8:56:00 PM