Author |
Topic |
|
rumpus
Starting Member
7 Posts |
Posted - 30 September 2008 : 01:52:25
|
Hi there, I've been trying for the past three days to do an install of the latest forum version with an SQL 2000 database on my local PC with no luck. I followed the great tutorial on upgrading from access to Microsft SQL posted in this forum (we currently run an access database).
I created a new SQL database in enterprise manager, created a new user with db_owner privilages on the database, set the conn string in config file to credentials of new user, run setup.asp?RC=5, fill in the setup form with my SA account and a default forum admin account but when I hit install I get the 'cannot open database' error when I know the conn string credentials should be fine. I understand this is probably a permissions problem but I can't work out why.
My aim is to create the database tables and then import the data from access but I can't get the database to connect so no install. I've tried finding a solution on the forums here but nothing has worked for me so far.
When doing an install of something like DotNetNuke my SA account credentials never fail to connect so in this case I must be missing something.
Would anyone have any advice on what I should try next? I'm really stuck.
Thanks very much.< |
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
rumpus
Starting Member
7 Posts |
Posted - 01 October 2008 : 01:25:16
|
Hi, sure can,
This is the message that comes up when it tries to instal: There has been an error !!
The database could not be opened !! Check your config.asp file and set the strConnString so it points to the database. Also check if strDBType is set to the right databasetype.
Code : 80004005
Error Description : [Microsoft][ODBC SQL Server Driver][Shared Memory]Invalid connection. < |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
rumpus
Starting Member
7 Posts |
Posted - 01 October 2008 : 05:34:47
|
Thanks, I've tried both SQL connection strings in the config (by the comments in the cofig file does the first SQL conn string use the OLEDB driver?) Anyway neither of them work. Anyway thanks for the link, I appreciate your time, I'l have a look through and see if I can figure it out :)< |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 01 October 2008 : 05:58:14
|
This is the connection string I recommend:
strConnString = "Provider=SQLOLEDB;Data Source=*****;database=***;uid=***;pwd=**;" '## MS SQL Server 6.x/7.x/2000 (OLEDB connection)
I suggested the article, because it explores several causes and provide solutions for them. It may be a good path to a solution.
How are you identifying the server in the connection string?< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
rumpus
Starting Member
7 Posts |
Posted - 01 October 2008 : 06:33:54
|
Thanks very much, I'll try the connection string you provided and see how it goes. It might be a couple of days for me to get to it as I have loads of projects on my plate at the moment so I'm not being rude, just busy as you are :)< |
Edited by - rumpus on 01 October 2008 06:34:40 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 01 October 2008 : 06:41:28
|
No problem. My guess would be that this is related to your SQL Server configuration (active network protocols) and the way you are identifying the server, but it's just a guess. A lot of other things may be happening.< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
rumpus
Starting Member
7 Posts |
Posted - 02 October 2008 : 19:54:14
|
OK, so I've been through the article you provided which was helpful. In the network utility I noticed that my server alias was not set to receive TCP/IP or Named Pipe connections which is weird because I can connect to it with other applications. I set this up but still can't open the database with either a TCP/IP or NP connection. I also tried pinging the server via the CMD. If I ping the server Alias (which is PC4) it pings fine but if I try to ping PC4\PC4 which is the actual server name it fails. I also can't ping my SQL Express server which makes me wonder if my DNS is set up properly. Do you know if you are supposed to ping the server alias or the actual server name?
This is from the server error logs which looks OK to me:
2008-09-11 03:11:48.99 server Server Process ID is 1776. 2008-09-11 03:11:48.99 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$PC4\LOG\ERRORLOG'. 2008-09-11 03:11:49.01 server SQL Server is starting at priority class 'normal'(4 CPUs detected). 2008-09-11 03:11:49.64 server SQL Server configured for thread mode processing. 2008-09-11 03:11:49.65 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks. 2008-09-11 03:11:49.90 spid2 Starting up database 'master'. 2008-09-11 03:11:51.01 server Using 'SSNETLIB.DLL' version '8.0.766'. 2008-09-11 03:11:51.01 spid5 Starting up database 'model'. 2008-09-11 03:11:51.03 spid2 Server name is 'PC4\PC4'. 2008-09-11 03:11:51.03 spid2 Skipping startup of clean database id 4 2008-09-11 03:11:51.04 spid2 Skipping startup of clean database id 5 2008-09-11 03:11:51.04 spid2 Skipping startup of clean database id 6 2008-09-11 03:11:51.04 spid2 Skipping startup of clean database id 7 2008-09-11 03:11:51.04 spid2 Skipping startup of clean database id 8 2008-09-11 03:11:51.04 spid2 Skipping startup of clean database id 9 2008-09-11 03:11:51.04 spid2 Skipping startup of clean database id 10 2008-09-11 03:11:51.21 server SQL server listening on xxx.xxx.x.xxx: 1433. 2008-09-11 03:11:51.21 server SQL server listening on 127.0.0.1: 1433. 2008-09-11 03:11:51.21 server SQL server listening on TCP, Shared Memory, Named Pipes. 2008-09-11 03:11:51.21 server SQL Server is ready for client connections 2008-09-11 03:11:51.34 spid5 Clearing tempdb database. 2008-09-11 03:11:52.40 spid5 Starting up database 'tempdb'. 2008-09-11 03:11:52.93 spid2 Recovery complete. 2008-09-11 03:11:52.93 spid2 SQL global counter collection task is created.
The xxxx's in the second IP have been put there by me for the purposes of this post. Sorry, I appreciate your help with this.< |
Edited by - rumpus on 02 October 2008 20:01:31 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 03 October 2008 : 11:18:32
|
You can't ping SQL Server, or any other port, for that matter. Ping doesn't allow you to specify a port. As SQL Server seems to be listening on the server address, do you have a firewall that may be rejecting connections to the computer?< |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Topic |
|