Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
CanadaDBA
583 Posts |
 Posted - 2008-10-02 : 07:56:10
|
| One of my SQL 2000 servers has started a weird attitude since last week. Its version is 8.00.2039 (SP4) on a Windows Server 2003 R2 Standard Edition SP2. Few days ago one of the applications started failing to connect to SQL Server. I wasn’t able to connect through Studio Management too. Later we found that we have to use port# 1350 in our ODBC connection. I checked the server and noticed the setting for TCP/IP “Network Protocol Default Value” is set to 1350 and there is no check for Hide server. I don’t know why the default is 1350 and not 1433.I also found that the Jobs screen does not refresh for those jobs which were created by Maintenance Plans. For example, it shows three jobs are still running but in fact they are not. And they didn’t run at all while they were supposed to run every night. I am not sure if it is related to the above port/connection issue. I just found that there is no history information for none of the jobs, either they are maintenance plan jobs or normal ones.Any idea/suggestions? Canada DBA |
|
|
RickD
Slow But Sure Yak Herding Master
3608 Posts |
Posted - 2008-10-06 : 16:56:46
|
| Strangely, it sounds like someone has moved the copy of SQL Server. The maintenence plan problem can be solved by changing the job to use:DTSRUN /N<packagename> /S /EInstead of the guid it uses currently.Not sure what your problem with the port is as not seen this before. |
 |
|
|
|
|
|
TCP/IP Port issue