EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB36499: Get error "Conversion failed when converting date and/or time from character string" when creating any object in a SQL Server metadata after upgrading to MicroStrategy 9.0.2.


Community Admin

• Strategy


Get the following error message when creating any object from Desktop after upgrading to MicroStrategy 9.0.2

SYMPTOM:
Get the following error message when creating any object from Desktop after upgrading to Strategy 9.0.2, as shown below:
 

ka04W000000OcU9QAK_0EM440000002HRg.png

 
The following error can be seen from the DSSError.log on Intelligence Server:
 
Sample Code/Error
2011-05-05 12:45:47.508-04:00 OdbcParameterizedQuery::ExecQuery failed. Error type: Odbc error. Odbc operation attempted: SQLExecute. Conversion failed when converting date and/or time from character string.Connection String: DSN=test;DESCRIPTION=Strategy ODBC Driver for SQL Server Wire Protocol;UID=test;WSID=test;DATABASE=test;ADDRESS=test, 1433;. SQL Statement: INSERT INTO DSSMDOBJINFO VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, UPPER(?), ?, ?, ?, ?, ?).
2011-05-05 12:45:47.530-04:00 Error executing SQL: INSERT INTO DSSMDOBJINFO VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, UPPER(?), ?, ?, ?, ?, ?) with parameters  ('38A062302D4411D28E71006008960167','77B9EF9A4AB91C0D66BF96A83D71C0B6',30,7680,N'QA_EM',N'',N'','BECF26C811E0772E248B00802FA76D42','73F748  2911D3596C60001B8F67019608','54F3D26011D2896560009A8E67019608',0,{ts'2011-05-05 15:45:47'},{ts'2011-05-05 15:45:47'},UPPER (N'QA_EM'),0,1033,0,0,N'') .
 
And the user notice there is no error message if executing the SQL above from DB Query tool from the Intelligence Server machine with the same DSN.
 
CAUSE: 
The "TraceDll" and "InstallDir" locations under section of the odbc.ini file is not updated to the new installation location after upgrading, as shown below:
Sample Code/Error
 
  Trace=0
  TraceFile=odbctrace.out
 
  TraceDll=/opt/mstr8/MicroStrategy/lib32/odbctrac.so
 
 
  InstallDir=/opt/mstr8/Strategy
 
  IANAAppCodePage=106
  UseCursorLib=0
 
ACTION:
Update the section of the odbc.ini file on Intelligence Server machine to match the new installation location, as shown below:
Sample Code/Error
 
  Trace=0
  TraceFile=odbctrace.out
  TraceDll=/opt/mstr9/MicroStrategy/lib32/odbctrac.so
  InstallDir=/opt/mstr9/Strategy
  IANAAppCodePage=106
  UseCursorLib=0
 
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

May 5, 2017

Last Updated:

May 5, 2017