SQL Server 2005 Developer: Database creation process

[Development]

I am trying to install 4.5.0 version on a Windows XP Professional under SQL SERVER 2005 Developer edition. During database creation process (step 7) system returns this error:

Creating Sugar configuration file (config.php)

Creating Sugar application tables, audit tables, and relationship metadata...

Creating the database sugar on portatil02...done
SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo. relationships... SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo.SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo.creating / relationship meta ... done
acl_roles... SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo.SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo.creating / relationship meta ... done
acl_actions... SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo.SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo.creating / relationship meta ... done
leads... SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo.SQL Error : El nombre de objeto 'SYSOBJECTS' no es vᬩdo.SQL Error : Se termin�� instrucci

Could you help me, please?

[Angel]

What happens if you run the following query from within SQL Management Studio?

SELECT * FROM SYSOBJECTS WHERE XTYPE = 'U'

[Development]

Many thanks for your attention.
If I run that query, this is what happens:

Error de ejecución SQL
Instrucción SQL ejecutada: SELECT * FROM SYSOBJECTS WHERE XTYPE = 'U'
Origen del error: .Net SqlClient Data Provider
Mensaje de error: El nombre del objeto 'SYSOBJETS' no es válido

Obviously, SYSOBJETCS table has not been created. What can I do now?
Thanks again

[Markku]

Maybe you could try to create the database before you start Sugar Setup Wizard?

[Angel]

Many thanks for your attention.
If I run that query, this is what happens:

Error de ejecución SQL
Instrucción SQL ejecutada: SELECT * FROM SYSOBJECTS WHERE XTYPE = 'U'
Origen del error: .Net SqlClient Data Provider
Mensaje de error: El nombre del objeto 'SYSOBJETS' no es válido

Obviously, SYSOBJETCS table has not been created. What can I do now?
Thanks again

Actually, I believe your problem lies elsewhere.

SYSOBJECTS is an internal table within MS-SQL. It always exists and contains a list of objects within a given database. The Sugar installer is trying to check if the Sugar tables already exist by looking for them in this catalog, but it is unable to read the catalog.

SQL 2005 allows MS-SQL admins to restrict access to these tables, which is a change in behavior from previous versions. Your issue seems to be coming from some of these security restrictions.

Do you get the same error message if you login to SQL Management Studio using "sa" and executing the same query?

If so, try changing SYSOBJECTS to SYS.OBJECTS. If it continues to fail, there is a different issue within the SQL server that we need to track down.

I suppose that you could always skip the part of the installer that checks for the Sugar tables, since you already know they are not there, but I wouldn't recommend you do that. Who knows what other items are inaccessible but necessary for normal operation.