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
9 subscribers
Views
9048 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 9 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
Parents
0
Eduardo Fuentes
Appian Employee
over 9 years ago
This confirms my theory. This is how you can fix the issue:
1. Make sure no k.exe is running (use Windows Task Manager to confirm)
2. Change the exension of server/process/exec/00/gw1/pe294.kdb to pe294.BAK
3. Change the exension of server/process/exec/01/gw1/pe294.kdb to pe294.BAK
4. Open a command prompt and run start-suite
5. Monitor the CPU and once it has gone down ~0% open the following command prompts (there will be a group of 32 minimized)
APP:PX*
wait until they all finish replaying transactions and show "Booted"
6. Once they all three show "Booted" you can run checkengine and confirm all engines are OKay.
7. Run stop-suite to do a proper shutdown
8. If this is successful you can now start the environment the normal way you do it
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 9 years ago
This confirms my theory. This is how you can fix the issue:
1. Make sure no k.exe is running (use Windows Task Manager to confirm)
2. Change the exension of server/process/exec/00/gw1/pe294.kdb to pe294.BAK
3. Change the exension of server/process/exec/01/gw1/pe294.kdb to pe294.BAK
4. Open a command prompt and run start-suite
5. Monitor the CPU and once it has gone down ~0% open the following command prompts (there will be a group of 32 minimized)
APP:PX*
wait until they all finish replaying transactions and show "Booted"
6. Once they all three show "Booted" you can run checkengine and confirm all engines are OKay.
7. Run stop-suite to do a proper shutdown
8. If this is successful you can now start the environment the normal way you do it
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data