Unable to initialize database, code: 1.Exception

Showing results for 
Search instead for 
Do you mean 
Reply
Participant II
Posts: 4
Registered: ‎12-24-2018
#1 of 3 534

Unable to initialize database, code: 1.Exception

2019-01-04 18:02:23,666 [Pipeline Execution Thread|INFO ] SessionStart: Setting Running Mode: OnPremises
2019-01-04 18:02:23,666 [Pipeline Execution Thread|INFO ] SessionStart: Installing data package
2019-01-04 18:02:23,978 [Pipeline Execution Thread|INFO ] SessionStart: Windows Server Version !>= Windows Server 2016.
Windows Defender Module is not present, cannot add Centrify exclusions to Windows Defender.
2019-01-04 18:02:23,978 [Pipeline Execution Thread|INFO ] SessionStart: Extracting Data components
2019-01-04 18:03:44,994 [Pipeline Execution Thread|INFO ] SessionStart: Updating UI components
2019-01-04 18:04:09,900 [Pipeline Execution Thread|INFO ] SessionStart: Updating App Template components
2019-01-04 18:04:18,853 [Pipeline Execution Thread|INFO ] SessionStart: Updating Tooling
2019-01-04 18:04:30,213 [Pipeline Execution Thread|INFO ] SessionStart: Initializing database in: C:\ProgramData\Centri
fy\Centrify Identity Platform\data\pgsqldb
2019-01-04 18:04:30,213 [Pipeline Execution Thread|INFO ] SessionStart: & "$initdb" -U "$dbuser" -A password -E UTF
8 --pwfile="$pwFile" -D "$dbDir"
initdb: could not create directory "C:/ProgramData/Centrify/Centrify Identity Platform/data": File exists
2019-01-04 18:04:34,150 [Pipeline Execution Thread|INFO ] SessionStart: Output from initdb: The files belonging to this
database system will be owned by user "administrator". This user must also own the server process. The database clust
er will be initialized with locale "English_United States.1252". The default text search configuration will be set to "
english". Data page checksums are disabled. creating directory C:/ProgramData/Centrify/Centrify Identity Platform/dat
a/pgsqldb ...
2019-01-04 18:04:34,307 [Pipeline Execution Thread|ERROR] SessionStart: Unexpected error during database host setup: Un
able to initialize database, code: 1.Exception
2019-01-04 18:04:34,307 [Pipeline Execution Thread|ERROR] SessionStart: at Centrify-InitializePgsql, C:\Program Files\C
entrify\Centrify Identity Platform\scripts\ps-module\Centrify.Cloud.Powershell.psm1: line 3160
at <ScriptBlock>, C:\Program Files\Centrify\Centrify Identity Platform\scripts\setup_cluster.ps1: line 172
2019-01-04 18:04:34,307 [Pipeline Execution Thread|ERROR] SessionStart: Timestamp: Fri, 04 Jan 2019 14:04:34 GMT

2019-01-04 18:04:34,338 [Pipeline Execution Thread|INFO ] SessionStart: No Windows Defender Module present, so none to
remove.

 

 

 

any suggestion on above error...

Centrify Guru I
Posts: 2,459
Registered: ‎07-26-2012
#2 of 3 532

Re: Unable to initialize database, code: 1.Exception

@Rameshwar,

 

Welcome to the community.

 

As a customer (or prospect) you should have access to the Support portal.  I'd work with them to collect logs and figure out the issue.

 

Perhaps you can give us some of the basics.

 

a) What version of PAS on premises are you installing?  Was this working before?

b) Is this a clustered setup or an evaluation?  Is this an upgrade? (from what version to what version?)

c) Is there proper name resolution for all the nodes and the service address?

d) Was PKI taken care of?  Are you using a proper certificate or are you trying to use a self-signed cert?

e) Are the Firewall communication ports (E.g. PostgreSQL port) open?

f) Is this a fresh installation or a re-installation?  (Did you properly cleanup the folders before reinstall?).

 

I highly-recommend that you work with your SE lead or SME for this.

 

R.P

Want to learn more about practical Centrify examples? Check out my blog at http://centrifying.blogspot.com
Follow Centrify:
Participant II
Posts: 4
Registered: ‎12-24-2018
#3 of 3 530

Re: Unable to initialize database, code: 1.Exception

i believe i found out the solution..if we login with doamin account then the installation is not working may be due to some permission issues...but once i login with local admin then it is working fine.

 

thanks for your reply