Link to home
Start Free TrialLog in
Avatar of daveyd123
daveyd123

asked on

Unable to uninstall or upgrade Veritas from Server 2003

OK...I had a Windows 2000 Domain controller with Veritas 9.0.  I demoted the Domain Controller to a member server.  I then upgraded W2k server to 2003 server leaving it as a member server but in a NEW domain.

Now none of the Veritas services will start.  When I try to start the Backup Exec Device and Media Service, I get the following "Error 1065:  The database specified does not exist"

When I go to uninstall Veritas completely it bombs out give me the message "Error 1606:  Could not access network location ECM"

When I try and upgrade to 9.1 it acts as if its upgrading...reboots the server and bombs.

Using the Veritas Repair it asks me to find the Backup Exec for Servers .msi file.  I point it to the msi and get the error message "1: 2755  2:  3  3:"    UGH

I need to get Backup Exec up and running as I have important backups to do!!!!
Avatar of daveyd123
daveyd123

ASKER

In the Backup Exec log I get this...

12-09-2004,17:26:56 :  DEBUG: Error 2755:  Server returned unexpected error 3 attempting to install package .
12-09-2004,17:26:56 :  ERROR: 1: 2755 2: 3 3:  


It also looks like that Windows Installer is corrupt on the server.  I tried running msiexec /unregister msiexec /regserver as well as installing Windows Installer 3.0.  Looks like none of that worked...
Avatar of Iamthecreator
This can be corrected by performing the following steps:
1. Right-click the Windows Start button and click Explorer
2. When the Windows Explorer window opens, right-click the WINNT folder, click Properties, and ensure the Read only checkbox is not selected
3. Go to the Security tab and ensure the Administrators group and System accounts have "Full Control" rights to the WINNT and WINNT\Installer folders and the Everyone group has "Read and Execute," "List Folder Contents," and "Read" permissions
Note: If the Installer folder is not visible within the WINNT folder in Windows Explorer, click the Tools drop-down menu, click Folder Options, then click View. Clear the Hide protected operating system files checkbox. The WINNT\Installer folder should now be present.
4. Once the above steps have been taken, the "Error 2755.1632" should no longer occur during the client installation.

Yea, I saw that on the Veritas support site....

System has full control of the winnt folder and it is not read only.  There is no "Installer" folder on any of my 2003 servers that run Backup Exec in the Winnt directory...Yes, I am viewing hidden files
**EDIT**

I do have the "Installer Folder" and yes, all the permissions are set correctly.  I even added the Everyone Group to the WINNT folder with the above permissions and it did not work.

Error" 12-09-2004,20:09:00 :  DEBUG: Error 2755:  Server returned unexpected error 3 attempting to install package .
         12-09-2004,20:09:00 :  ERROR: 1: 2755 2: 3 3:"
Open Services and check under "Logon" for all your Backup Exec services. Make sure these are either set to the "Local System Account" or a backup authorized account of your new domain. It is likely you have it set to the old Account which doesn't exist anymore. If you are going to use a user account you should use the following format:
DomainName\AccountName.

You will also have to supply the correct password.

If possible I'd use the local system account, as otherwise you will have to change the passwords via "services" everytime the user changes the password.
The manual uninstall proceedure for versions 7 and 8 might help, http://seer.support.veritas.com/docs/199301.htm. Of course it is different services you have to remove from the registry but the proceedure for 9.0 should be fairly similar.
Rindi...

That was the first think I checked.  I used the local system credentials as well as my domain admin credentials to try and start the services.  Each time I get the same error "1065:  The database specified does not exist"
hi, there

How about tricking the Registry and delete the Veritas and try reinstalling the Veritas ?..
Can you at least open Backup Exec? If so you should be able define your catalog path via tools, options.
cooledit...

I deleted as many Backup Exec registry keys I could find.  Then tried to reinstall 9.1 and get an error message.

Rindi...

Backup Exec would not open at all.  
What error message?
Rindi..

Error 1935:  an error occurred during the installation of assemble component {a lot of numbers and letters}

Here is the solution from Veritas  http://seer.support.veritas.com/docs/259027.htm    however I am not running Terminal Services on the Server.

I did copy the contents of the CD to the local drive and ran setup.exe...and it failed.  Here is the log file from Veritas...


-- LOGGING STARTED -- (12/13/04 11:01:08)
(12/13/04 11:01:08)  Executing Custom Action VerifyVxSDMVer with target VxSDM_VerifyVersions.
-- LOGGING FINISHED -- (12/13/04 11:01:08)

-- LOGGING STARTED -- (12/13/04 11:01:11)
(12/13/04 11:01:11)  Executing SetCustomActionData_MSI for VxSDM.
(12/13/04 11:01:11)  MsiGetProperty of SetCustomActionData returned:  0
(12/13/04 11:01:11)  Setting property ConfigVxSDM to:  TOKEN-INSTALLDIR:C:\Program Files\VERITAS\VERITAS Update\
(12/13/04 11:01:11)  MsiSetProperty of SetCustomActionData returned:  0
(12/13/04 11:01:11)  SetCustomActionData_MSI returning:  0
-- LOGGING FINISHED -- (12/13/04 11:01:11)

-- LOGGING STARTED -- (12/13/04 11:01:11)
(12/13/04 11:01:11)  Executing Custom Action PrepVxSDM with target VxSDM_PrepVxSDM.
(12/13/04 11:01:11)  Executing SetVxSDMRegKeys.
(12/13/04 11:01:11)  MsiGetPropery returned 0 and got ProductCode {EFE295A9-C617-4ECE-A191-14265F5BD7ED}
(12/13/04 11:01:11)  MsiGetPropery returned 0 and got INSTALLDIR C:\Program Files\VERITAS\VERITAS Update\
(12/13/04 11:01:11)  MsiSetProperty returned 0 and set ARPINSTALLLOCATION to C:\Program Files\VERITAS\VERITAS Update\
(12/13/04 11:01:11)  MSI_AddToRegistryTable returned 0 for InstallPath
(12/13/04 11:01:11)  MSI_AddToRegistryTable returned 0 for Last Taskbar HWND
(12/13/04 11:01:11)  MSI_AddToRegistryTable returned 0 for Installed Product Code
(12/13/04 11:01:11)  SetVxSDMRegKeys returning:  0
(12/13/04 11:01:11)  SetVxSDMRegKeys returned:  0
(12/13/04 11:01:11)  PrepVxSDM returning:  0
-- LOGGING FINISHED -- (12/13/04 11:01:11)

-- LOGGING STARTED -- (12/13/04 11:01:12)
(12/13/04 11:01:12)  Executing CA ConfigVxSDM with target VxSDM_ConfigVxSDM.
(12/13/04 11:01:12)  Calling RegisterDlls
(12/13/04 11:01:12)  Executing RegisterDlls
(12/13/04 11:01:12)  Executing GetInstallPath(TCHAR * strInstallPath,INT buffSize,MSIHANDLE hDBase)
(12/13/04 11:01:12)  MsiGetProperty returned 0 getting CustomActionData of TOKEN-INSTALLDIR:C:\Program Files\VERITAS\VERITAS Update\
(12/13/04 11:01:12)  TOKEN-INSTALLDIR is C:\Program Files\VERITAS\VERITAS Update
(12/13/04 11:01:12)  Returning install path:  C:\Program Files\VERITAS\VERITAS Update
(12/13/04 11:01:12)  GetInstallPath returing:  0
(12/13/04 11:01:12)  GetInstallPath-1 returned:  0
(12/13/04 11:01:12)  Install path:  C:\Program Files\VERITAS\VERITAS Update
(12/13/04 11:01:12)  Short Install path:  C:\PROGRA~1\VERITAS\VERITA~1
(12/13/04 11:01:12)  Doing Registration with:  C:\PROGRA~1\VERITAS\VERITA~1\VxSDMCom.dll
(12/13/04 11:01:12)  Executing DoRegistration

-- LOGGING STARTED -- (12/13/04 11:01:12)
(12/13/04 11:01:12)  COM:  DllMain Entry.
(12/13/04 11:01:12)  COM:  Attaching to process.
(12/13/04 11:01:12)  Library C:\PROGRA~1\VERITAS\VERITA~1\VxSDMCom.dll
(12/13/04 11:01:12)  GetProcAddress succeeded.
(12/13/04 11:01:12)  COM:  Registering VxSDM COM object.
(12/13/04 11:01:12)  COM:  DllMain Entry.
(12/13/04 11:01:12)  COM:  Detaching from process.
-- LOGGING FINISHED -- (12/13/04 11:01:12)
(12/13/04 11:01:12)  DoRegistration returning:  0
(12/13/04 11:01:12)  DoRegistration returned:  0
(12/13/04 11:01:12)  RegisterDlls returning:  0
(12/13/04 11:01:12)  RegisterDlls returned:  0
(12/13/04 11:01:12)  Calling RegisterWithVxSDM
(12/13/04 11:01:12)  Executing GetInstallPath(TCHAR * strInstallPath,INT buffSize,MSIHANDLE hDBase)
(12/13/04 11:01:12)  MsiGetProperty returned 0 getting CustomActionData of TOKEN-INSTALLDIR:C:\Program Files\VERITAS\VERITAS Update\
(12/13/04 11:01:12)  TOKEN-INSTALLDIR is C:\Program Files\VERITAS\VERITAS Update
(12/13/04 11:01:12)  Returning install path:  C:\Program Files\VERITAS\VERITAS Update
(12/13/04 11:01:12)  GetInstallPath returing:  0
(12/13/04 11:01:12)  GetInstallPath-1 of RegisterWithVxSDM returned:  0
(12/13/04 11:01:12)  Initializing COM now.
(12/13/04 11:01:12)  Creating instance of CLSID_VxSDManager now

-- LOGGING STARTED -- (12/13/04 11:01:12)
(12/13/04 11:01:12)  COM:  DllMain Entry.
(12/13/04 11:01:12)  COM:  Attaching to process.
(12/13/04 11:01:12)  Initializing Database
(12/13/04 11:01:12)  Getting System Directory.
(12/13/04 11:01:12)  Getting next available default database
(12/13/04 11:01:12)  Initializing Database
(12/13/04 11:01:12)  Getting System Directory.
(12/13/04 11:01:12)  Getting next available default database
(12/13/04 11:01:12)  Constructing Inventory Manager.
(12/13/04 11:01:12)  Setting Database name to:  inventorydb.xml
(12/13/04 11:01:12)  Getting VXSDM COM Installation Directory.
(12/13/04 11:01:12)  Querying registry key Software\Classes\CLSID\{1788BE74-7061-468C-AF85-6C8D6A702689}\InprocServer32 for value Default
(12/13/04 11:01:12)  Setting Database path to:  C:\PROGRA~1\VERITAS\VERITA~1
(12/13/04 11:01:12)  Setting Database name to:  plugins.xml
(12/13/04 11:01:12)  Getting VXSDM COM Installation Directory.
(12/13/04 11:01:12)  Querying registry key Software\Classes\CLSID\{1788BE74-7061-468C-AF85-6C8D6A702689}\InprocServer32 for value Default
(12/13/04 11:01:12)  Setting Database path to:  C:\PROGRA~1\VERITAS\VERITA~1
(12/13/04 11:01:12)  Initializing Database
(12/13/04 11:01:12)  Getting System Directory.
(12/13/04 11:01:12)  Getting next available default database
(12/13/04 11:01:12)  Constructing DistManager Object.
(12/13/04 11:01:12)  Setting Database name to:  distdb.xml
(12/13/04 11:01:12)  Querying registry key SOFTWARE\VERITAS\VxUpdate for value InstallPath
(12/13/04 11:01:12)  Initializing Client Manager
(12/13/04 11:01:12)  Initializing Task Scheduling Manager
(12/13/04 11:01:12)  Initializing Inventory Manager.
(12/13/04 11:01:12)  Initializing Inventory Manager Object.
(12/13/04 11:01:12)  Opening Database.
(12/13/04 11:01:12)  Loading database from file.
(12/13/04 11:01:12)  Getting Database path:  C:\PROGRA~1\VERITAS\VERITA~1
(12/13/04 11:01:12)  Getting Database name:  inventorydb.xml
(12/13/04 11:01:12)  Getting file size of file:  C:\PROGRA~1\VERITAS\VERITA~1\inventorydb.xml
(12/13/04 11:01:12)  Getting status of file:  C:\PROGRA~1\VERITAS\VERITA~1\inventorydb.xml
(12/13/04 11:01:12)  Opening Database.
(12/13/04 11:01:12)  Loading database from file.
(12/13/04 11:01:12)  Getting Database path:  C:\PROGRA~1\VERITAS\VERITA~1
(12/13/04 11:01:12)  Getting Database name:  plugins.xml
(12/13/04 11:01:12)  Getting file size of file:  C:\PROGRA~1\VERITAS\VERITA~1\plugins.xml
(12/13/04 11:01:12)  Getting status of file:  C:\PROGRA~1\VERITAS\VERITA~1\plugins.xml
(12/13/04 11:01:12)  Initializing Distribution Manager.
(12/13/04 11:01:12)  Initializing DistManager.
(12/13/04 11:01:12)  Opening Database.
(12/13/04 11:01:12)  Loading database from file.
(12/13/04 11:01:12)  Getting Database path:  C:\WINNT\system32
(12/13/04 11:01:12)  Getting Database name:  distdb.xml
(12/13/04 11:01:12)  Getting file size of file:  C:\WINNT\system32\distdb.xml
(12/13/04 11:01:12)  Getting status of file:  C:\WINNT\system32\distdb.xml
(12/13/04 11:01:12)  Client Manager initializations successful.
(12/13/04 11:01:12)  Registering inventory module C:\Program Files\VERITAS\VERITAS Update\vxsdmdiscovery.dll
(12/13/04 11:01:12)  COM:  AddInventoryModule Entry
(12/13/04 11:01:12)  COM:  Adding module C:\Program Files\VERITAS\VERITAS Update\vxsdmdiscovery.dll
(12/13/04 11:01:12)  Registering inventory module:  C:\Program Files\VERITAS\VERITAS Update\vxsdmdiscovery.dll
(12/13/04 11:01:12)  Opening Database.
(12/13/04 11:01:12)  Loading database from file.
(12/13/04 11:01:12)  Getting Database path:  C:\PROGRA~1\VERITAS\VERITA~1
(12/13/04 11:01:12)  Getting Database name:  plugins.xml
(12/13/04 11:01:12)  Getting file size of file:  C:\PROGRA~1\VERITAS\VERITA~1\plugins.xml
(12/13/04 11:01:12)  Getting status of file:  C:\PROGRA~1\VERITAS\VERITA~1\plugins.xml
(12/13/04 11:01:12)  Looking for module: C:\Program Files\VERITAS\VERITAS Update\vxsdmdiscovery.dll
(12/13/04 11:01:12)  COM:  AddInventoryModule returning 0
(12/13/04 11:01:12)  AddInventoryModule returned:  0
(12/13/04 11:01:12)  Terminating the Inventory Manager.
(12/13/04 11:01:12)  Terminating Inventory Manager Object.
(12/13/04 11:01:12)  Closing Database.
(12/13/04 11:01:12)  Closing Database.
(12/13/04 11:01:12)  Terminating the Distribution Manager.
(12/13/04 11:01:12)  Terminating DistManager Object.
(12/13/04 11:01:12)  Closing Database.
(12/13/04 11:01:12)  Client Manager termination successful.
(12/13/04 11:01:12)  Terminating Task Scheduling Manager.
(12/13/04 11:01:12)  Uninitialized Task Scheduling Manager complete.
(12/13/04 11:01:12)  Uninitialized Client Manager complete.
(12/13/04 11:01:12)  Destructing DistManager Object.
(12/13/04 11:01:12)  Destroying Database Object.
(12/13/04 11:01:12)  Destroying Inventory Manager Object.
(12/13/04 11:01:12)  Destroying Database Object.
(12/13/04 11:01:12)  Destroying Database Object.
(12/13/04 11:01:12)  COM:  DllMain Entry.
(12/13/04 11:01:12)  COM:  Detaching from process.
-- LOGGING FINISHED -- (12/13/04 11:01:12)
(12/13/04 11:01:12)  RegisterWithVxSDM returning:  0
(12/13/04 11:01:12)  RegisterWithVxSDM returned:  0
(12/13/04 11:01:12)  ConfigVxSDM returning:  0
-- LOGGING FINISHED -- (12/13/04 11:01:12)
Well nothing from Veritas or Dell support worked.  Blew away the server, reinstalled Server 2003 and Veritas 9.1...works like a charm
ASKER CERTIFIED SOLUTION
Avatar of CetusMOD
CetusMOD
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial