I replaced my temporary license with permanent license and did configuration(./c

shanmukhaprasads over 10 years ago

I replaced my temporary license with permanent license and did configuration(./configure.sh) and deployed both Jboss &Appian.

After doing configuration , if i tried to start .start-suite.sh or stop-suite.sh or check-engine.sh all are saying k3.lic

Please let me know after replacing with permanent license shall i need to do anything more ? Thanks

Discussion posts and replies are publicly visible

0 abhi.jana
Appian Employee
over 10 years ago

Check if the new license k3.lic has been deployed to <APPIAN>/server/_bin/k/linux64
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shanmukhaprasads over 10 years ago

yes , it's deployed properly and even able to get the support number when i ran ./k but after deploying the changes using ./configure.sh file its giving this problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhi.jana
Appian Employee
over 10 years ago

Is this a distributed environment? The license deployment and start/stop/checkengine all need to be run on the server hosting the Engines
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shanmukhaprasads over 10 years ago

No, if i don't do any configuration after replacing permanent license everything is going as usual but it causes with deployment changes , Do you need any log info ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhi.jana
Appian Employee
over 10 years ago

Perhaps the k3.lic has not been updated in the Repository and the configure script is copying the old k3.lic file replacing the new one.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shanmukhaprasads over 10 years ago

Yeah, even i'm thinking the same. Do you have any idea to erase old license details ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhi.jana
Appian Employee
over 10 years ago

Replace the old k3.lic in <REPO>/server/_bin/k/linux64 with the new one and deploy the configurations.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shanmukhaprasads over 10 years ago

I did the same but no use. Do anyone have any idea about this ?
Thank you
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shanmukhaprasads over 10 years ago

Solved Problem by replacing license within configuration repository and appian folder
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 shanmukhaprasads over 10 years ago

Thanks Abhi for the Info
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel