Installation issue

[msammoud]

Dear All

I 'am happy to to join this forum and i hope found every time a solution :)

I have a issue with the installation of symantec exec 2012 , every time the installation is stopped and does not move on the step when sql server 2005 express try to install.

I use windows server 2008 R2 64bit

please find below more detail on the link: 

http://www.imagup.com/data/1174051032.html

Any advice please.

Best regards

Mohamed

[CraigV]

Hi. Any AV on that server? If so, stop it and try the installation again. The other alternative is to install SQL Express manually from the installation DVD and then try the installation again. Thanks!

[lmosla]

Hi,

if there is still a problem after CraigV's suggestions have been tried I have had success by  following the solution listed here http://www.symantec.com/business/support/index?page=content&id=TECH64580&actp=search&viewlocale=en_U...

and here is another good link to use if needed:http://www.symantec.com/business/support/index?page=content&id=TECH56006

[msammoud]

Dear all

I tried to install the BE , the same issue still exist, i find the log file error (below)

2013-01-29 13:02:21.78 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\BKUPEXEC ].

2013-01-29 13:02:21.78 Server      Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.

2013-01-29 13:02:21.78 Server      The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x490, state: 1. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.

2013-01-29 13:02:21.78 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.

Any help please about this message ?

Regards

Mohamed

[CraigV]

...is this with a normal domain administrator account? And you aren't pointing it to any SQL server...this is a local installation of SQL Express right?

[msammoud]

Hi

a message appeare before in the environnement check : 

------------------------------------

warning

  The current user is not allowed to connect to SQL Server instances denoted by "**". To select an instance of SQL Server for use with Backup Exec, do one of the following ways:

- Use an account that has access to the high instance of SQL Server

- Allow the current user to connect to the SQL Server instance

Check Backup Exec SQL 2000

-----------------------------------

I 'am connected with installer account (with administrator right)

Regards

Mohamed

[CraigV]

...OK...so you're using a domain administrator and installing the SQL Express version on the disk. Have you tried to install SQL Express by itself and then followed up with an installation of BE?

[CraigV]

Here are some links to these SQL errors you are getting? Doesn't appear to be BE-related:

http://blogs.technet.com/b/mdegre/archive/2009/11/20/the-sql-network-interface-library-was-unable-to-register-spn.aspx

http://social.msdn.microsoft.com/Forums/eu/sqlexpress/thread/1f4c5c53-bc8e-4f38-84b7-01d352f556b0

Thanks!

[msammoud]

Hi

Yes of course, I tried to install sql server 2005 without BE, but it crached on this step without any error message: find attachment

http://www.imagup.com/data/1174134530.html

Any advice please

Best regards

Mohamed

[msammoud]

Good Mrning support

Any Update about this issue?

Regards

Mohamed

[msammoud]

Good Mrning support

Any Update about this issue?

Regards

Mohamed

[CraigV]

Have you tried to install to a different drive?

Also hit the support flag for you.

Thanks!

[Colin_Weaver · Accepted solution]

Please log a formal support case for us to do more in depth analyis (the forums are community based pages that have contributions by support staff but may not be able to always identify or fix a given condition)

[msammoud]

good afternoon 

Ahh ok.. Sorry for all, i will contact the symantec support

Best regards

Mohamed