would new virus protection block startup? 2

[naselle]

The store computer recently had a virus , so a computer guy came to fix it. He cleaned things up and installed a new virus protection, but now we cannot connect to the POS system. When I go to connect, it gives an error message that says "cannot connect to the database". I also tried disabling the new virus protection and then connecting and that didn't work. Do you think it could be fouling things up? What should I try?
thank you so much...Lori

 

[mrdenny]

OK, excellent. We are making progress. So we can see the computer (that's what the PING command tells us), but we can't see the database for some reason.

Open up the new anti-virus (what did he install). Is there any sort of firewall shown in here? If so disable the firewall. You'll also want to go into the Control Panel (Start > Control Panel) and disable the Windows Firewall if that is enabled. (We can try turning these back on later, but first things first.)

Once you've got any/all firewalls disabled, from the Control Panel again, open up Administrative Tools and open Services. Find the "SQL Server Service" and right click on it and select stop. When the popup box closes, right click on it again and click start. Then go back to the other computer and try the telnet test again. If you get an blank box with a flashing cursor that's a good sign.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[naselle]

I couldn't find the SQL server service. I disabled the firewalls (2) then went to Administrative tools, Services, but SQL server services wasn't an option...

 

[gmmastros]

IF you're using SQL2000, the name of the service will be MSSQLSERVER.



-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[naselle]

The services box doesn't come up on the store computer. I ran the same steps on the back office computer and was able to scroll down to the MSSQL - the description was blank - the startup was on automatic and the last column said local system just like all the others.

 

[naselle]

so - I went ahead and tried the stop and stop thing (on the back office computer) - then the telnet test on both computers and got the same error message.

 

[naselle]

I think it is kinda weird that the services box won't open at all on this computer....

 

[mrdenny]

Naselle,
So both computers have SQL installed on them?

I don't think I'm clear on the setup you've got. Let me explain how I think everything is setup, and you can let me know where I'm incorrect.

You have two computers. One named POS and one named DF4STL21. The database for the POS software is installed on the computer named POS. You have the software to lookup inventory and ring up sales installed on both the POS computer and the DF4STL21 computer. The POS computer is working, and the DF4STL21 computer is not working and giving the error message about not being able to connect to the database.

Does all that sound correct?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[naselle]

No, - the POS is the hardware store computer that runs the whole point of sale program with scanner. I have a back room office with another computer that is connected and can share files including the retail management system "manager" and "admistrator" but not the one that rings up sales. I could get into customer accounts and settings and what not - just not the "sales" part of the system - before this mix up. Now - the back office computer looks like it is running - but when I click on it to start it up it just sits there and doesn't connect. (but the little icon shows that it is running. The POS computer on the other hand has a little icon that says "not connected".
I hope that makes sense......

 

[mrdenny]

ok, and the database is on which machine, the POS, or the machine in the back room named DF4STL21?

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[Rosburg]

Database is on the POS machine.

 

[mrdenny]

And the POS machine can't get it it's own database. OK, then the network stuff we've been looking at we don't need to worry about for now. Let's focus on getting the software on the POS machine connected to the local database.

On the POS machines can you find the ERRORLOG file (the one without .1, .2, etc and post it please.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[gmmastros]

I wonder....

If this computer (POS) is using DHCP, and the restarts caused it to get a different IP Address, perhaps that would cause the problem. I mean.... if the old IP Address was x.x.x.1 and now it's x.x.x.2, but the DNS was cached to point to the old IP Address (which no longer exists).... maybe, just maybe!

If I am right, you may be able to solve the problem by doing this:

Click Start -> Run
Type CMD
Click OK

Type: ipconfig /flushdns
Hit Enter

If I am wrong, running this command will have no adverse affects. I suppose it's worth a try.


-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[Rosburg]

Either I or Naselle will look for this in the morning at store opening. The store is closed for the day, or I would go look now.

 

[mrdenny]

Not a problem. We can continue tomorrow.

The ipconfig couldn't hurt. But at the moment our problem is the local server connection. That's where we'll start tomorrow then.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[Rosburg]

I can confirm it's using DHCP. Will try flushing dns.

 

[gmmastros]

our problem is the local server connection

I get that. But, if the application is trying to connect based on computer name, and the dns entries are mangled so that it points to a different (perhaps non-existent computer), wouldn't that explain the issue?

Denny, you clearly have a ton more experience in this area. I'm just curious.



-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom

 

[mrdenny]

I suppose that it could. It's not very likely as the OS should know that the name that is being looked for, and pull the IP from the local settings instead of polling the network for it. Then the TCP connection would be redirected to local host instead of to the nic. But if for some reason, this layer wasn't working correctly (and something's funky since the Services window didn't want to open) then it could do a polling on the network for the name and come up blank.

It is worth trying, and certainly can't do any harm. I'm thinking a reboot for the POS computer may be in order as well. I want to take a peek at the ERRORLOG file I think first.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog

 

[naselle]

you guys are great - thank you so much - here is the error log without extension

2009-08-12 10:24:13.32 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)

2009-08-12 10:24:13.32 server Copyright (C) 1988-2002 Microsoft Corporation.
2009-08-12 10:24:13.32 server All rights reserved.
2009-08-12 10:24:13.32 server Server Process ID is 684.
2009-08-12 10:24:13.32 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2009-08-12 10:24:13.37 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2009-08-12 10:24:13.62 server SQL Server configured for thread mode processing.
2009-08-12 10:24:13.65 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2009-08-12 10:24:13.71 spid4 Starting up database 'master'.
2009-08-12 10:24:14.01 server Using 'SSNETLIB.DLL' version '8.0.766'.
2009-08-12 10:24:14.01 spid5 Starting up database 'model'.
2009-08-12 10:24:14.04 spid4 Server name is 'POS'.
2009-08-12 10:24:14.04 spid4 Skipping startup of clean database id 4
2009-08-12 10:24:14.07 spid4 Skipping startup of clean database id 5
2009-08-12 10:24:14.07 spid4 Skipping startup of clean database id 6
2009-08-12 10:24:14.07 spid4 Skipping startup of clean database id 7
2009-08-12 10:24:14.14 server SQL server listening on 192.168.7.102: 1433.
2009-08-12 10:24:14.14 server SQL server listening on 127.0.0.1: 1433.
2009-08-12 10:24:14.14 server SQL server listening on TCP, Shared Memory, Named Pipes.
2009-08-12 10:24:14.14 server SQL Server is ready for client connections
2009-08-12 10:24:14.18 spid5 Clearing tempdb database.
2009-08-12 10:24:14.62 spid5 Starting up database 'tempdb'.
2009-08-12 10:24:14.73 spid4 Recovery complete.
2009-08-12 10:24:14.73 spid4 SQL global counter collection task is created.
2009-08-12 12:11:06.60 server SQL Server terminating because of system shutdown.

 

[naselle]

ok - I did this step - should I shut down and restart?

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\OFFICE> ipconfig/flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Documents and Settings\OFFICE>

 

[gmmastros]

There's no need to restart the computer. Just check your app to see if it's working.


-George

"The great things about standards is that there are so many to choose from." - Fortune Cookie Wisdom