Veritas on Windows 2003 domain controller

  • Thread starter Thread starter Spale
  • Start date Start date
S

Spale

I'm trying to install Veritas Back Exec 9.1 on my Windows 2003 server acting
as domain controller.

First event is:

MsiInstaller Event ID 1015

Failed to connect to server. Error: 0x800401F0



Then MsiInstaller Event ID 11707



1: 2: VERITAS Backup Exec for Windows Servers 3: 1: 1707





Then MsiInstaller Event ID 11708

Product: Microsoft SQL Server Desktop Engine -- Installation operation
failed.



What is the problem?
 
The error code 0x800401F0 is CO_E_NOTINITIALIZED which indicates that OLE has
not been initialized. This can commonly occur when MsiOpenPackage or
MsiOpenProduct are called from threads that have not initialized OLE.

How is the installation work? Are other MSI application installs affected?

- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.

MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>
 
spale,

What is your status on this issue? Could you please update and share
as there are others in need of a resolution.

I have a similar problem installing 9.1 Admin Console on a Win XP
Validating the BE msi package (VERITAS Backup Exec for Window
Servers.msi) using Full MSI Validation Suite/Orca, returns a hug
amount of errors and warnings like these:

ICE03 WARNING String overflow (greater than length permitted i
column); Table: Component, Column: KeyPath, Key(s)
mediarequiredforrecovery_en.rpt.4720227D_76B6_4279_B0D3_C95B9D1310BE

ICE30 ERROR The target file '0tandqic.sy_' is installed i
'[ProgramFilesFolder]\VERITAS\BACKUP~1\NT\idr\disk4\' by two differen
components on an SFN system
'IDR_0tandqic.sy_.4720227D_76B6_4279_B0D3_C95B9D1310BE' an
'IDR4_0tandqic.sy_.1B15BB01_8E2D_4A12_A3E6_175864F3EF67'. This break
component reference counting.

On a Windows Server 2003 where the BE 9.1 media server is installed al
hotfixes and SP1 installs fail and aborts at 99% when BE services ar
to be started. All is rolled back.

Regards
M Ross
*I'm trying to install Veritas Back Exec 9.1 on my Windows 200
server acting
as domain controller.

First event is:

MsiInstaller Event ID 1015

Failed to connect to server. Error: 0x800401F0



Then MsiInstaller Event ID 11707



1: 2: VERITAS Backup Exec for Windows Servers 3: 1: 1707





Then MsiInstaller Event ID 11708

Product: Microsoft SQL Server Desktop Engine -- Installatio
operation
failed.



What is the problem?
Click to expand...


-
rosmo0
 
Carolyn,

I am getting the exact same errors when trying to install Veritas
Backup Exec 9.1

It seems to fail when installing the MSDE instance, log file snippet
below:
=== Logging stopped: 6/3/2004 9:40:07 ===
MSI (s) (AC:78): Note: 1: 1708
MSI (s) (AC:78): Product: Microsoft SQL Server Desktop Engine --
Installation operation failed.

I also get the same Event log entries as Spale did.

Any further information on this?

I have tried re-registering MSI service using:
msiexec /unreg
msiexec /regserver

I have been in contact with Veritas support, but they indicate that it
is becoming a Microsoft Error, not a Vertias one....

Any help would be greatly appreciated.
 
3xtr3m0 said:
Carolyn,

I am getting the exact same errors when trying to install Veritas
Backup Exec 9.1

It seems to fail when installing the MSDE instance, log file snippet
below:
=== Logging stopped: 6/3/2004 9:40:07 ===
MSI (s) (AC:78): Note: 1: 1708
MSI (s) (AC:78): Product: Microsoft SQL Server Desktop Engine --
Installation operation failed.


Any update on the above ?? We have the exact same issue and can'
install MSDE on W2003 Server
Click to expand...



-
diacono
 
Hey guys. I've just had this problem. Mine was after removing BE 9.1 and
then trying to reinstall so may differ slightly to yours. But I had
exactly the same error in the log: 1708...

Basically I made sure there were no dead reg entries for either the
MSDE or BE 9.1.

I then dumped the bkupinst.log and MSDE_BKUPEXEC.log.

Then I deleted the entire contents of the TEMP dir under the
administrator local settings dir and the contents of the Local
Settings\Application Data\ApplicationHistory.

After that the install went ahead perfectly.

This was on one of our production Windows 2003 domain controllers.

BE 9.1 is now functioning fine.

I hope this helps.

Rob

[B]> > 3xtr3m0 said:
*Carolyn,

I am getting the exact same errors when trying to install Veritas
Backup Exec 9.1

It seems to fail when installing the MSDE instance, log file
snippet
below:
=== Logging stopped: 6/3/2004 9:40:07 ===
MSI (s) (AC:78): Note: 1: 1708
MSI (s) (AC:78): Product: Microsoft SQL Server Desktop Engine --
Installation operation failed.


Any update on the above ?? We have the exact same issue and can't
install MSDE on W2003 Server. *>
Click to expand...
Click to expand...
 
Spale said:
*I'm trying to install Veritas Back Exec 9.1 on my Windows 200
server acting
as domain controller.

First event is:

MsiInstaller Event ID 1015

Failed to connect to server. Error: 0x800401F0



Then MsiInstaller Event ID 11707



1: 2: VERITAS Backup Exec for Windows Servers 3: 1: 1707





Then MsiInstaller Event ID 11708

Product: Microsoft SQL Server Desktop Engine -- Installatio
operation
failed.



What is the problem? *
Click to expand...

I had the same problem when trying to apply sp1 or add a license key t
backup exec, no matter what i tried it didnt work until i got on th
console itself and ran the install from there.

It was a w2k server in remote admin mode, try to go directly to the bo
not using ts (dont know if you did


-
FlemmingRii
 
Yeah I was doing it all from a Admin Mode TS session. I never trie
doing it on the console and since I finally got it to install I can'
try it again. Would make sense to try from the console though I kno
several other issues where installations via TS fail....

Rob
*I had the same problem when trying to apply sp1 or add a license ke
to backup exec, no matter what i tried it didnt work until i got o
the console itself and ran the install from there.

It was a w2k server in remote admin mode, try to go directly to th
box not using ts (dont know if you did)
Click to expand...


-
chonta
 
chontay said:
*Yeah I was doing it all from a Admin Mode TS session. I never trie
doing it on the console and since I finally got it to install I can'
try it again. Would make sense to try from the console though I kno
several other issues where installations via TS fail....

Rob *
Click to expand...

tried a few times after on a test box and its the same story if its o
w2k ill try on w2k3 later , from file/regmon it looks like it get
confused over %temp% is a \1 or \2 director


-
FlemmingRii
 
Hi All,
I encounter the same problem on 2 different Windows 2003 server. So
contacted Microsoft and they finally found me the solution after
weeks of research. The problem came from the MSDE component.

Microsoft provide me a new semnt.dll file and also a procedure t
reinstall MSDE properly.

The procedure was this one :

On c: i go in program file folder ans i create manually a folder calle
'Microsoft SQL Server' than inside i create 2 folder called '80' an
'MSSQL$BKUPEXEC'

Into '80' folder in create also 'Tools' folder and inside this one
create also 'Binn'

Into MSSQL$BKUPEXEC folder i create another 'Binn' folder.

Into the 2 different 'Binn' folder i copy the semnt.dll file tha
microsoft provided to me.

I start the backup Exec 9.1 installation normally with defaul
parameter and everythin is OK.

I you need the semnt.dll file you can contact me.

Regard


-
Shark
 
Hi,

Apologies about the mess-up in my earlier reply.. Please ignore it.
I'm having the same problem. Could you please mail the semnt.dll t
me.

My email is (e-mail address removed)

Cheers

Har


-
Har
 
I am having the same problem. Please send me the patched SEMNT.DLL fil

(e-mail address removed)
thank


-
trda
 
chontay said:
*Hey guys. I've just had this problem. Mine was after removing BE 9.
and then trying to reinstall so may differ slightly to yours. But
had exactly the same error in the log: 1708...

Basically I made sure there were no dead reg entries for either th
MSDE or BE 9.1.

I then dumped the bkupinst.log and MSDE_BKUPEXEC.log.

Then I deleted the entire contents of the TEMP dir under th
administrator local settings dir and the contents of the Loca
Settings\Application Data\ApplicationHistory.

After that the install went ahead perfectly.

This was on one of our production Windows 2003 domain controllers.

BE 9.1 is now functioning fine.

I hope this helps.

Rob *
Click to expand...


Do you remember what you searched for in the registry? I searched fo
Veritas, but what did you search for for MSDE.

When you say you dumped the logs, you deleted them?

thanks in advance,

(e-mail address removed)


-
dicespic
 
Hi Sharki,

Can you please provide me with the semnt.dll file you got from MS. I
been working on my installation for weeks now without success.

Thanks,
 
I have been reading the responses by everyone and I thought I would pos
the link to a solution that I found
http://seer.support.veritas.com/docs/265613.htm
You will still need to contact Microsoft for the hotfix and let the
know that you are referencing the KB article # 829386. The most direc
number I have found to the SQL support group is 1-800-936-5800 option 3

Kyl


-
Kyle
 
Hi Sharki,

Would you email me the MS semnt.dll file
to (e-mail address removed)? I am having the same issue and your assistance i
greatly appreciated.

many thanks,

Bill
*Hi All,
I encounter the same problem on 2 different Windows 2003 server. So
contacted Microsoft and they finally found me the solution after
weeks of research. The problem came from the MSDE component.

Microsoft provide me a new semnt.dll file and also a procedure t
reinstall MSDE properly.

The procedure was this one :

On c: i go in program file folder ans i create manually a folde
called 'Microsoft SQL Server' than inside i create 2 folder calle
'80' and 'MSSQL$BKUPEXEC'

Into '80' folder in create also 'Tools' folder and inside this one
create also 'Binn'

Into MSSQL$BKUPEXEC folder i create another 'Binn' folder.

Into the 2 different 'Binn' folder i copy the semnt.dll file tha
microsoft provided to me.

I start the backup Exec 9.1 installation normally with defaul
parameter and everythin is OK.

I you need the semnt.dll file you can contact me.

Regards
Click to expand...


-
whermac
 
Sharki said:
*Hi All,
I encounter the same problem on 2 different Windows 2003 server. So
contacted Microsoft and they finally found me the solution after
weeks of research. The problem came from the MSDE component.

Microsoft provide me a new semnt.dll file and also a procedure t
reinstall MSDE properly.

The procedure was this one :

On c: i go in program file folder ans i create manually a folde
called 'Microsoft SQL Server' than inside i create 2 folder calle
'80' and 'MSSQL$BKUPEXEC'

Into '80' folder in create also 'Tools' folder and inside this one
create also 'Binn'

Into MSSQL$BKUPEXEC folder i create another 'Binn' folder.

Into the 2 different 'Binn' folder i copy the semnt.dll file tha
microsoft provided to me.

I start the backup Exec 9.1 installation normally with defaul
parameter and everythin is OK.

I you need the semnt.dll file you can contact me.

Regards *
Click to expand...

Could you please email me the semnt.dll file. Email t
(e-mail address removed)

Thks a lot


-
pmoriso
 
Back
Top