Error 25623 while installing
-
Hi!
I tried to install Project Server 2003 using SQL Server 2000 SP4 as database. During the installation I get an 25623-error (something like SQL Database does not exist or no connection established).
Weird thing: The databases and the users project server is supposed to create ARE created!
Google didn't tell me much about the 25623-error, maybe someone here knows something??!
The SQL Server 2000 SP4 has been de-installed and re-installed once on this machine. Since then I experienced some search problems on my Sharepoint, but I thought it was a sharepoint-error. Now I think that I may have forgotten something to make a clean de-installation. I used the "Remove Programs"-feature in the control panel of Win2003; I guess that may not have been enough.
Any ideas?
Thanks in advance!
-
You need the SQL Server 2000 setup CD to uninstall. But, before you try that, if the database definitely does exist, then it's probably just a login or permissions thing. Does the login that you supplied during installation (of Project Server) have access to (and the necessary permissions in) the database? Or, if you are using Windows authentication, does your account have access to the database in SQL Server?
John
-
Well, it should have...
I'll try one more time, maybe I didn't use the right user everywhere I could've...
Is there no other way to fix this except a full re-installation? This SQL Server is also used by our Sharepoint and except the Search everything works fine...
-
I don't know anything about Project Server or Sharepoint, but it sounds likely to me that you've got a perfectly good SQL Server installation and that reinstalling it may not solve your problem. Use Profiler and sp_who while you are trying to install Project Server to see who is connected and what they're doing.
Do you have a test server you can try it on as well?
John
-
This IS my test server...and the productive server (the real productive server hasn't been installed yet, so we're using this one for now).
An alternative would be a Virtual Server. I tried that as well but I hit a snag with the Project Server/Sharepoint-integration there that looked like a specific problem to the virtual server configuration that I cannot solve (long story short: Restrictive network policies), so I tried to install everything on one real server...
What's "Profiler" and "SP_Who"?
-
Profiler is a diagnostic tool that records events that happen on SQL Server. You will find it in your Start menu, in the same place as Enterprise Manager and Query Analyzer. sp_who is a stored procedure that lists all the connections to the server at the time it is run; it is the equivalent of clicking on Process Info in Enterprise Manager. Both of these techniques should be able to tell you whether your login has a connection to the server and what sort of activity it's performing. You'll find more information on them in Books Online, the Microsoft website and other web resources.
Good luck!
John
-
It works now!
There was no problem with SQL Server. I checked everything and it was OK. The problem was the Project Server.
It seems that Microsoft Project Server 2003 requires a special SQL Server admin account for the installation and for that your SQL Server has to use "mixed mode"-authentication. My SQL Server was using "Windows only"-authentication. I switched it to "mixed mode", added a new admin user - and it worked.
Weird thing: Why would a Microsoft-product require "mixed mode"?! I thought they did everything with "Windows"-authentication and active-directory-users (like in Sharepoint, MS CRM etc.)...weird...
Anyway, thanks for your help, John!
-
Happy to help - can't explain the Microsoft thing, though!
John
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply