BE Server service will not start

[Rob_Hack]

Hi,
I am testing the eval of 11d.
We are currently running 8.6 and were going to upgrade to 10d however I ran into some problems regarding the install:

http://forums.symantec.com/discussions/thread.jspa?threadID=69242&tstart=120

As that post mentioned, I've ran thru various support docs. I also opened a case via email support but that did not solve the issue. Email support is not available for 11d so I am posting here

We then decided to ditch 10d and eval 11d however I am getting the same issue after the install/ reboot (I uninstalled 8.6 and installed 11d cleanly).

My log files show:

Event Type:Information
Event Source:Backup Exec
Event Category:(65535)
Event ID:33152
Date:07/12/2006
Time:11:08:04
User:N/A
Computer:XXXXXX
Description:
Adamm Database Event: Open Database Connection ...
Error = S_OK
Server = "XXXXXX"
Active Node = ""
Instance = ""
Database = "BEDB"
Connection String = "DRIVER=SQL Server;SERVER=XXXXXX;DATABASE=BEDB;App=BEWS PVL"

Event Type:Information
Event Source:Backup Exec
Event Category:(65535)
Event ID:33152
Date:07/12/2006
Time:11:08:05
User:N/A
Computer:XXXXXX
Description:
Adamm Database Event: Open Database Connection Success!
Error = S_OK
Server = "XXXXXX"
Active Node = ""
Instance = ""
Database = "BEDB"
Connection String = "DRIVER=SQL Server;SERVER=XXXXXX;DATABASE=BEDB;App=BEWS PVL"

Event Type:Information
Event Source:Backup Exec
Event Category:(65535)
Event ID:57345
Date:07/12/2006
Time:11:08:12
User:N/A
Computer:XXXXXX
Description:
Database Exception Context:{? = CALL DBO.SAVEOWNERSHIP(?,?,?,?,?,?,?)} Error:-536837662: :: -2147217900:Must declare the variable '@timestamp'. :: DB Error Set 0: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@timestamp'. :: DB Error Set 1: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@Timestamp'.



Event Type:Information
Event Source:Backup Exec
Event Category:(65535)
Event ID:57345
Date:07/12/2006
Time:11:08:12
User:N/A
Computer:XXXXXX
Description:
Database Exception Context:Ownership Insert Error:-536837662: :: -2147217900:Must declare the variable '@timestamp'. :: DB Error Set 0: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@timestamp'. :: DB Error Set 1: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@Timestamp'.



Event Type:Information
Event Source:Backup Exec
Event Category:(65535)
Event ID:57345
Date:07/12/2006
Time:11:08:13
User:N/A
Computer:XXXXXX
Description:
Database Exception Context:{? = CALL DBO.SAVEMACHINEEX(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)} Error:-536837662: :: -2147217900:Must declare the variable '@timestamp'. :: DB Error Set 0: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@timestamp'. :: DB Error Set 1: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@ID'. :: DB Error Set 2: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@Timestamp'.



Event Type:Information
Event Source:Backup Exec
Event Category:(65535)
Event ID:57345
Date:07/12/2006
Time:11:08:13
User:N/A
Computer:XXXXXX
Description:
Database Exception Context:MachineEx Insert Error:-536837662: :: -2147217900:Must declare the variable '@timestamp'. :: DB Error Set 0: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@timestamp'. :: DB Error Set 1: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@ID'. :: DB Error Set 2: native=0x89 source=Microsoft OLE DB Provider for SQL Server hr=0x80040e14 Must declare the variable '@Timestamp'.



Event Type:Error
Event Source:Backup Exec
Event Category:(65535)
Event ID:57802
Date:07/12/2006
Time:11:08:13
User:N/A
Computer:XXXXXX
Description:
The Backup Exec Server Service did not start. An internal error (-536837662) occurred in object 11.

We currently already have sql2000 installed running business critical databases (some standard web databases and SmartStream) so modification of these is not really an option.

The database gets created in sql however there is obviously a problem with the stored procedure.

I have tried a repair of the installation but to no avail and have uninstalled and reinstalled using the sql express option. This seems to have worked however I am unsure of any problems running sql2000 and sql express on the same box.
Also we would prefer to use an existing instance

Our existing sql2000 configuration is:
Server default collation
Latin1-General, binary sort

Because of the above sql issues, the BE server service will not start.
Can anyone help?
thanks

[Daniel_Blake]

I just worked through a different problem with upgrading to BE 11d and the BE services not starting. It's a little different than yours but the cause might be the same.

If you had a previous version of BE installed on that server your registry has path values pointing to Program Files\Veritas\
(these don't get removed during an uninstall or replaced during the 11d install)

I edited these paths in the registry and BE 11d starts just fine. If you need me to find the exact spots in the registry where these are hiding let me know and I'll get on it.

Hope this helps.
Daniel Blake
Milford Central School

[Nick_Pearce]

Daniel,

Could you possibly post the key locations as I have a feeling I may be experiencing the same issue

[Rob_Hack]

Thanks for your help Daniel.
I checked this and it didn't work. I'm afraid I didn't think it would anyway as the event logs indicate that this is more of a problem with the way that the SQL stored procedure in BE11 is trying to do something.
Cheers anyway

[Rob_Hack]

Well after all this we appear to have found the problem.
The coding in the sql stored procedures is inconsistent in terms of case sensitivity.
This would not be a problem except if your existing sql instance has to be case sensitive for another application, as is our case.

So, we will install a non case sensitive instance and test on this.
I do feel that either symantec should state that the instance should not be case sensitive or work on getting the coding consistent.

[shweta_rege]

Hello,


Could you please update us on the issue?


Can we close the post now?



Thank You,

Shweta