source:
VMware vCenter Server 5.5.0 (Windows 2012R2, MSSQL 2012 Express), 12GB RAM

target:
VMware vCenter 6.0 U3 Appliance (Linux, PostgreSQL), 16 GB RAM

 

Error:

  • Firstboot script execution error
  • This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request
  • /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log
  • install.ciscommon.internal.error
  • This vCenter Server has extensions registered that cannot be upgraded to or may not work with the new vCenter Server. Extensions: VR Management (by VMware, Inc.) on http://vcenter:80/|https://appliancevr:8043 VMware vSphere Update Manager Extension on https://vcenter:8084/vci/sdk vCenter Operations Manager (by VMware, Inc.) on https://new_vcenter/vcops-vsphere/viClientConfig.xml

 

Znalezione obrazy dla zapytania vcenter fastboot failed

 

on logs:

csd.txt :
[2018-05-23 15:28:44] [INFO] Web Socket Server [50100] Terminated With no error code
[2018-05-23 15:28:44] [INFO] CSD Server Exited.
[2018-05-23 15:28:44] [INFO] Lookup: stop called…
[2018-05-23 15:28:44] [INFO] Lifetime: join…
[2018-05-23 15:28:47] [INFO] Lifetime Timer stopped.
[2018-05-23 15:28:47] [INFO] Lifetime: Exited.
[2018-05-23 15:28:47] [INFO] Lookup: Exited.
[2018-05-23 15:28:47] [INFO] ~MigrationApi
[2018-05-23 15:28:47] [INFO] Process exiting.
vcsa_0001.txt:
2018-05-23 14:47:23.065316 CIP Service [VCSA INFO] nfc.vmGetFile: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5509″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”cQk5-Fj2d-VuiB-e1PL”,”result”:”{\n \”status\”: \”error\”, \n \”info\”: [], \n \”question\”: null, \n \”progress_message\”: {\n \”args\”: [\n \”VMware Postgres\”\n ], \n \”id\”: \”install.ciscommon.component.starting\”, \n \”localized\”: \”Starting VMware Postgres…\”, \n \”translatable\”: \”Starting %(0)s…\”\n }, \n \”warning\”: [], \n \”error\”: {\n \”resolution\”: {\n \”id\”: \”install.default.failure.resolution\”, \n \”localized\”: \”This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.\“, \n \”translatable\”: \”This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request.\”\n }, \n \”detail\”: [\n {\n \”args\”: [\n \”see /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log\”\n ], \n \”id\”: \”install.ciscommon.internal.error\”, \n \”localized\”: \”Encountered an internal error.\\n\\nsee /var/log/firstboot/vpostgres-firstboot.py_16503_stderr.log\“, \n \”translatable\”: \”Encountered an internal error.\\n\\n%(0)s\”\n }\n ], \n \”componentKey\”: \”vpostgres\”, \n \”problemId\”: null\n }, \n \”progress\”: 48\n}”,”isFinal”:”true”}
2018-05-23 14:47:23.068319 Progress Page: [VCSA ERROR] – First Boot error
2018-05-23 14:47:28.784075 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5515″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”D2ER-tpuj-51BF-Unl0″,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:47:30.187195 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5515″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”D2ER-tpuj-51BF-Unl0″,”result”:””,”isFinal”:”true”}
2018-05-23 14:47:30.191199 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:48:10.911286 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5521″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”fNmx-IuPq-78cR-k5BZ”,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:48:12.316936 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5521″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”fNmx-IuPq-78cR-k5BZ”,”result”:””,”isFinal”:”true”}
2018-05-23 14:48:12.320941 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:48:53.037021 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5527″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”u4fv-YEyW-ODJE-aHO5″,”result”:””,”isFinal”:”false”,”item”:[“{\”error\”:\”vim.fault.FileNotFound\”}”]}
2018-05-23 14:48:54.440281 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5527″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”u4fv-YEyW-ODJE-aHO5″,”result”:””,”isFinal”:”true”}
2018-05-23 14:48:54.443297 Progress Page: [VCSA ERROR] Error in downloading support bundle
2018-05-23 14:49:38.771027 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”false”,”item”:[“{\”data\”:\”\”}”]}
2018-05-23 14:49:39.573271 CIP Service [VCSA INFO] nfc.vmGetSupportBundle: {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”true”}
2018-05-23 14:49:39.577275 Progress Page: [USER INFO] Support bundle created successfully – {“type”:”result”,”statusCode”:”PROCESS_STATUS”,”sessionId”:”VUWL-RKh1-ot5F-ysjh”,”requestId”:”5534″,”requestComponentId”:”fileTransfer”,”requestObjectId”:”tfqA-CRMH-XOIh-bOXA”,”result”:””,”isFinal”:”true”}
2018-05-23 15:14:49.825467 Progress Footer: Closing the installation wizard

 

what to check:

  1. Check DNS, forward and reverse resolution
  2. Check NTP server, try to sync time
  3. Plug-in not compatible is better to unregister/uninstall:  how to.
    I uninstalled: Update Manager, Operations Manager, UCS Plugin, VR Plugin
  4. In our environment Replication Appliance was incompatible with new version of vCenter. I stopped all replication jobs, unregistered Appliance (how to). Stopped VR Appliance.
  5. Check the database size…

 

Resolution:

In my situation, 8GB database (MSSQL) on Win2012R2 with 12GB RAM (small vCenter, 1000VM), was migrated to the same, small vCenter on Linux (1000 VM), with 16 GB RAM.

… it was to small.
I modified: vCenter Server to 32GB RAM,
on migration step I choose Large vCenter (32GB RAM) to create large vCenter Appliance

Success :)

ps. after this, I downsized RAM to 16GB :)

 

VMware Appliance size

 

RESULT:

VMware Migration result

 

 

Advertisements

SkipRearm – use Windows without activating

When evaluation period is expired, and you cannot rearm OS, then change registry key:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\SoftwareProtectionPlatform\

 

change value of SkipRearm to 1

 

tested on Win2012R2

Problem:

Type: Consistency check Status: Failed Description: DPM cannot continue protection for VMware <vm_name> on <vCenter_server/ESX host IP>  (ID 30184) More information End time: 2018-03-12 23:48:37 Start time: 2018-03-12 23:48:37 Time elapsed: 00:00:00 Data transferred: 0 MB Cluster node – Source details: <vm_name> Protection group: Protection Group 1 Items scanned: 0 Items fixed: 0

 

Resolution:

Problem with VM *.vmx file.

  • Delete vmx and recreate VM
    or
  • create new VM and bind hdd from old VM.

System Center Data Protection 2016

SC-SQL – IP: 10.45.1.200
SC-DPM – IP: 10.45.1.201

Problem:

Installing DPM and connecting it to remote SQL, I’ve got error 812

System Center DPM 2016 Install Error ID: 812

Report configuration failed. Verify that SQL Server Reporting Services is installed properly and that it is running. ID: 812 . When installing Data Protection Manager DPM  common installation error system admins encounter is ID: 812. This is caused by the SQL Server Reporting Services misreading the reporting database.

 

Cause:

Changed account which runs service: Reporting Service

 

Resolution:

Start -> Reporting Services Configuration Manager -> Encryption Keys -> Delete Encrypted Content (click: Delete) -> Change (click: Change) – generates new encryption keys :)

 

Now you may resume installation of DPM :)

  • DBCC DBCC CHECKDB (<db name>)
  • DBCC CHECKDB
  • DBCC CHECKDB (<db name>, REPAIR_ALLOW_DATA_LOSS | REPAIR_FAST | REPAIR_REBUILD)
  • DBCC CHECKCONSTRAINTS
  • search constraints in DB by name:
    SELECT * FROM INFORMATION_SCHEMA.REFERENTIAL_CONSTRAINTS
    WHERE CONSTRAINT_NAME =’FK_Documents_Finance’

 

 

Problem:

Restore >1GB database dump;

  • phpmyadmin – too slow, errors, php.ini modifications etc.
  • mysqldump – slow, errors ex. BLOB

 

Solution:

  • create empty database, for example by phpmyadmin
  • connect to it:

mysql -u usertest -p databasetest

  • type path to db dump:

source /backup/databasetest_2017-10-01.sql

 

Output:

You will see progress like:

Query OK, 7146 rows affected (0.42 sec)
Records: 7146 Duplicates: 0 Warnings: 0

 

 

Problem:

The connection cannot be completed because the remote computer that was reached is not the one you specified. This could be caused by an outdated entry in the DNS cache. Try using the IP address of the computer instead of the name.


Solution:

Time difference. Sync clock :)