D
Dan Triant
OK, So I have SQL Server 2005 Beta on a 2003 SE server, IIS and everything
setup and Sharepoint running smooth. I have followed instructions to the best
that I can figure, and for some reason at the step WEBSPS.SQL the SETUPDB.CMD
errors. The setup starts and does run code for quite some time, and then
fails with error "Msg 156, Level 15, State 1, Server <servername>, Procedure
MSP_WEB_SP_QRY_GetTasksIDs, Line 24 Incorrect Syntax near the keyword
'index'. 1> 2> 3> Error encountered while running WEBSPS.SQL! Press any
key to contunue......"
I get this on both last months and this months install for Project 2003
server Eval DVD's and cant figure what is causing this to fail when all of
the others seem to run fine. I even tried to run the upgrade even though
this is a First install and get the same error.
Any help is greatfully appreciated, I am current just going to download the
60 day trial from MS, just thought I would see if anyone had some idea to
what would cause this. My only thought would be that the SQL server is a
BETA, however I could not find anything on this being an issue....
setup and Sharepoint running smooth. I have followed instructions to the best
that I can figure, and for some reason at the step WEBSPS.SQL the SETUPDB.CMD
errors. The setup starts and does run code for quite some time, and then
fails with error "Msg 156, Level 15, State 1, Server <servername>, Procedure
MSP_WEB_SP_QRY_GetTasksIDs, Line 24 Incorrect Syntax near the keyword
'index'. 1> 2> 3> Error encountered while running WEBSPS.SQL! Press any
key to contunue......"
I get this on both last months and this months install for Project 2003
server Eval DVD's and cant figure what is causing this to fail when all of
the others seem to run fine. I even tried to run the upgrade even though
this is a First install and get the same error.
Any help is greatfully appreciated, I am current just going to download the
60 day trial from MS, just thought I would see if anyone had some idea to
what would cause this. My only thought would be that the SQL server is a
BETA, however I could not find anything on this being an issue....