Home › Forums › Deployments › Environments › Server console not starting
Tagged: Staging Session CRM
- This topic has 4 replies, 3 voices, and was last updated 8 years, 9 months ago by Aravinddokala.
-
AuthorPosts
-
-
November 12, 2015 at 9:25 am #381AravinddokalaMember
Dear Team,
I have restored some db details at my local-dev environment of SQL server. I have selected the environment, user and tried to start server console. The server console throws the below error and shutdowns automatically. PFA server log and environment file and please suggest the solution.12ERROR::Error: Error getting User from User Registry during login of "nexjsa"; check the SOA connection. If the User Registry is mixed-in to this model, then the account configured to access the User Registry must be a LocalUser. (fail.User.cannotGetUserFromRegistry)Thanks,
Aravind0 -
November 14, 2015 at 2:28 pm #383Ed ShawKeymaster
This question has been answered.
Overview:
The Environment file was missing some SOA Service Connection settingsEnvironment files are where you put all of the configuration settings for a particular server environment. e.g. Local Development, QA, Staging…
Some of the settings include Connections, which are deployment settings for Datasources, Channels and SOA. For each datasource (e.g. relational database), channel (e.g. MessageQueue or HTTP channel), or SOA Service specified in the model that you are using in your environment you need to have an entry with correct location, ports, credentials, etc.
Typically when you have a problem like this it manifests itself as an error in the server log at startup that will point you to the DataSource, Channel or SOA Service that you need to look at settings for.
1 -
November 15, 2015 at 10:32 am #385AravinddokalaMember
Additional Info ::
123456789101112131415161718192021222324251. Test connection was successful from Nexj-Studio.2. PFB version details of restored DB and nexJ model version--Confirm NexJ version of dB schemas/Instancesselect * from DUGQ_NexJCRM..NJVersion;421.551.1303.118.39_R6_1_1_M1-3select * from DUGQ_NexJStage..NJSVersion;421.551.1303.118.39_R6_1_1_M1-3select * from DUGQ_NexJBI..NJBIVersion;BI DB was not restored due to space constraint--Full List of versions to checkselect * from njversion;421.551.1303.118.39_R6_1_1_M1-3select * from msgversion;5select * from cnvversion;421.551.1303.118.39_R6_1_1_M1-3select * from urversion;8select * from njsversion; ( not from back up db)421.551.1303.118.39_R6_1_1_M1-3select * from njbiversion;nexj model version:421.551.1303.118.39_R6_1_1_M1-3Please suggest on the error mentioned.
0 -
November 15, 2015 at 10:57 am #387Ed ShawKeymaster
Do you have an example of an environment file on another machine that is working with your checked-out code? I’m wondering if you should be using perimiter auth rather than basic. e.g.
123456SOAConnection auth="perimeter" binding="context" service="nexj:soa:Registry:1.0">Properties>Property name="system" value="#t"/>/Properties>/SOAConnection>SOAConnection auth="perimeter" binding="context" service="nexj:soa:UserRegistry:1.0">** note: removed the beginning <'s so it wouldn't be interpreted as markup.
0 -
November 15, 2015 at 12:37 pm #389AravinddokalaMember
Dear EdShaw,
thanks for the response;
the problem lies at environment file where all the required data-sources need to define as according to the project design and also need to create missing Database and created few db tables. Later, disabled the data-source. Need to refresh and restart the serve. that works!
Regards,
Aravind0
-
-
AuthorPosts
- You must be logged in to reply to this topic.