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
29 replies
Subscribers
7 subscribers
Views
10362 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Appian Primary DS is working. Getting the following error: java.lang.
GouthamKrishna
over 10 years ago
Appian Primary DS is working. Getting the following error:
java.lang.IllegalStateException: [jdbc/primaryds] The schema is invalid.
Please let me know, what can be done to solve this error...
OriginalPostID-117700
OriginalPostID-117700
Discussion posts and replies are publicly visible
0
clintont
over 10 years ago
Where would i find the output?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
clintont
over 10 years ago
I beleive this is what you are looking for?
sail_state_cache.xlsx
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
clintont
over 10 years ago
Updating attachment.
sail_state_cache.xlsx
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Do you see how my query showed your column is of type image? (see your first output in the XSLX) Even if your other query shows varbinary(max) the one I sent you shows it's an image.
Can you expliclity run:
ALTER TABLE sail_state_cache ALTER COLUMN entry_value varbinary(max) NOT NULL
and try restarting the app server?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
pattye
over 10 years ago
I ran that statement, but the output from sp_columns continues to show the TYPE_NAME as an image.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
pattye
over 10 years ago
FYI, I am working on this with Clinton.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Did you try restarting JBoss after running the "ALTER TABLE" command? It should start now based on my testing.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 10 years ago
Further investigation revealed this happens if you are using and old version of the JDBC driver for SQL Server. You should use version 4.0
www.microsoft.com/.../details.aspx
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
pattye
over 10 years ago
Thanks Eduardo. We are now using Oracle instead of SQL Server, but good information for anyone else upgrading.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<