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

10.422: Database Write-back: Transaction Services


Stefan Zepeda

Salesforce Solutions Architect • Strategy


Learn how to save and store business decisions and initiate transactions in your mobile apps. Create mobile applications with write-back enabled functionality (transactions) for extended business value. Build workflows with stored procedures, input dependent text, and transactional SQL.

SYMPTOM:
When users attempt to connect to a project source, the following error message is received:

ka02R000000kVcHQAU_0EM440000002GKF.gif

Metadata Server cannot connect to metadata repository. {SQL Driver Error} Cannot find the input table or query 'DSSMDSYSPROP' (or other metadata table name). Make sure it exists and the name is spelled correctly.
The previous message appears with Microsoft Access; however, error messages similar to the one below appear with other databases, in this case with SQL Server:

ka02R000000kVcHQAU_0EM440000002GK5.gif

CAUSE:
DSSMDSYSPROP is the first metadata table accessed by Strategy Developer when a Project Source is opened.
The error message occurs because the metadata tables do not exist in the location Strategy Developer has been configured to use.
This may occur if the correct metadata prefix is not being used. It may also occur if the DSN used to connect to the metadata is not configured to point to the correct database.
 
ACTION:
The following procedure describes how to resolve the issue.

  1. Right-click on the Project Source in Strategy Developer and select 'Modify Project Source.' Verify that the correct Metadata prefix is entered on the last tab of the Project Source Manager.
  2. If the correct Metadata prefix is entered, open Strategy Test ODBC from Program Files->Strategy ->Tools->ODBC Test Tool. Using the DSN, login, and password that are specified for the problematic Project Source, connect to the location where the metadata tables reside. Verify that the following SQL runs successfully: Select * from DSSMDSYSPROP. If the table can not be found, check with the DBA to ensure the login being used is able to view the metadata tables.

Comment

0 comments

Details

Knowledge Article

Published:

April 27, 2017

Last Updated:

April 27, 2017