Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
7 subscribers
Views
2206 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Error :The import of dataStore could not be finalized: The data store was save
swatis552
over 11 years ago
Error :The import of dataStore could not be finalized: The data store was saved but cannot be published: The data source [jdbc/SqlServerDataSource] cannot be reached or its configuration is invalid. Details: Could not find datasource
The following error was displayed when the application was imported with Data Store whereas when we removed the data store from the package the application was imported successfully.
Please suggest....
OriginalPostID-96780
OriginalPostID-96780
Discussion posts and replies are publicly visible
0
Sathya Srinivasan
Appian Employee
over 11 years ago
You may want to check if the database configuration is correctly set up on your target environment. The easiest way to do this is to create a temporary data store and try to persist some sample info in there.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rahulk828
over 11 years ago
Thanks Sathya for the reply. Let me just elaborate the problem statement: We have two instance of Appian 7.3 one with Sql Server as Database while other has MySQL DB. We have developed application on one of the appian instance with SQLSERVER as the database while importing the same on the other instance with MysQL as DB. We are getting exception as mentioned above. Is it like if two instance of appian are using different databases then one cannot import into the other database.Or some other reason. Please guide.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Sathya Srinivasan
Appian Employee
over 11 years ago
Different databases should not cause any issue like this as there is an ORM tier in the middle that handles translation. What you do need to verify is if the database is correctly configured. For e.g. is the JNDI names the same for the two instances you are trying to work on and things like that. This is why I suggested you check the datastore configuration first. Did you manage to do that?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
rahulk828
over 11 years ago
Thanks again. Database in both the instances are configured properly as different application with datastores are working fine on the both the instance. We faced issue while moving the application from one instance(SqlServer) to another(Mysql). Moreover the JNDI names are different over both the instances. Is this can be the issue?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel