SQL Server 2005 installed on Windows Vista Ultimate
When I try to start the agent, it return with the message that the service started and then stopped. On investigation I found that the Windows Event Log service won't start, returning the error:
"error 4201: the instance name passed was not recognized as valid by a WMI
data provider"
(I have posted this on Windows Vista forums but had no response).
I have just installed SQL Server 2005. The machine had an expired version of SQL Express on it which I removed. Now when i go to open the Management Studio it says it can't connect. When I check the service, it is set to automatic using the local account but is not running. When I start it, it throws an error stating that it started and then stopped. The first error record in the log file states:
Server TCP provider failed to listen on [ 'any' <ipv4> 1433]. Tcp port is already in use.
Could this be causing the problem? How do I check to see what is using 1433? In general, what the heck did I do wrong during the install? One article said something about the new installation thinking it was still the expired version. Could there be something left in the registry from the old version of Express causing this?
I am trying to move SQLMail from a standard SQL 6.5 server to a virtual clustered SQL Server. The exchange profile has been set up and the services are running on a domain login. Exchange is also running as a clustered service which is being used successfully from the standalone SQL Server with SQL Mail.
However, when the SQL Mail service is started on the Clustered SQL Server, the service starts for about 5 seconds and then stops. The logs report that SQL Mail started but no messages are recorded to state that why the service has stopped again.
The request failed with HTTP status 405: Method not allowed. (Microsoft.ReportingServices.SemanticQueryDesign)
------------------------------
When I checked services I realised that Reporting Services wasn't started. I tried starting it and received a message:
"The Sql Server Reporting Services (MSSQLServer) started and then stopped. Some services stop automatically if they have no work to do.........."
I also tried to start the service from Configure Report Server and received an error:
"System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed. at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout) at ReportServicesConfigUI.Panels.ServerInformationPanel.StartStopServiceTask(Boolean start)"
Any idea why this is happening? Should I install SP2?
I've got a couple of jobs who have a odbc connection to a AS400 machine. But when these jobs run they won't stop anymore. I've got to stop these jobs manually so that the next day the jobs can start again as scheduled. The jobs did run all the packages succesfully. Does somebody know how this is possible? It did work fine but since a couple of weeks they just won't stop anymore. I hope you can help me! :S
Hello everyone. I'm having a problem with the sql server agent occasionally not executing its scheduled jobs, and unless the sql server agent is restarted they will not execute according to their schedule. I've read many posts on people having problems with running a package manually and then not being able to run it in a job, although that is not my problem since these are jobs that have all run successfully historically, and only until the agent is restarted do they start working again. It is the strangest thing.....we have many different jobs on this server and all of them will just mysteriously stop being executed. Two other things of note, the agent and server processes both run on AD accounts, and we receive this error:
SQL Server Scheduled Job 'X' - Status: Failed - Invoked on: 2007-10-27 02:00:00 - Message: The job failed. Unable to determine if the owner (ADadacct) of job 'X' has server access (reason: Unable to connect to server - check SQL Server and SQL Server Agent errorlogs).
In SQL 2000 you can schedule a job to run each time the agent starts. I don't see that option now in 2005.
Does anyone know what happened to that or how to achieve that. I could do a stored proc with the proc option I guess but why did they remove that functionality or maybe I am not seeing it.
I have database on SQL Server 2000 set up with a merge publication.This publication is configured with a number of dynamic filters toreduce the amount of data sent to each client. Each client has ananonymous pull subscription. The merge process can be triggered by thewindows sync manager and my application.To improve performance I have created some helper tables to hold themapping between user login and primary keys of selected entities.For the replicated data to be correct the contents of the helper tablesneeds to be up to date.I need to fire off a stored procedure on the publisher beforereplication starts to verify that this data is up to date. I can notsee any documented way of doing this however I have been experimentingwith some unorthodox systems.Firstly has anyone any ideas?I have been considering adding a trigger to some of the tables used bythe Microsoft replication code - yes I know this is very nasty.My problems arise because executing this stored procedure will causesome data to be updated. In updating data we could create a newgeneration in the database. I must therefore run my stored procedurebefore any the Microsoft code makes any generation checks / updates.Anyone done anything similar, Anyone have any better ideas?Any comments would be gratefully received.
I have a laptop with vista and sql 2005. When i start my computer, after it boots up and is ready to go, I look in the task manager at the process tab. Some sort of SQL Server component is running and eating up about 50k's worth of memory. What is it and how do set either Vista or SQL Server to not start whatever this is unless I do it manually(oh yeah...how would I turn it on?)and what are the ramifications of not having it start up when i start my laptop?
I know it is a rather rambling question, but its the best I can describe it. Thanks in advance for your help!
I have a job I want to run everyday but before this job starts and I want to check and see if another job has completed before I start this job. i would like to do this in the job steps in SSMS. step 1 is job 'xxxxxxx' running if no go to step 2 if yes exit
I have a table in sql server 2000 which has a column whose name starts with a number("2ndName").I have a c# code which updates the table by filling a Dataset.When I issue an update, it throws the following error:-"Incorrect Syntax near 2"Query I use to build the adapter is "SELECT id, Name, [2ndName] FROM MyTBL WHERE 1 = 3" and the statement issued to update is "objAdapter.Update(objDSDB, "MyTBL")" when it throws the error "Incorrect Syntax near 2".Any help to resolve this is appreciated.Thanks in advance.Jai
We have two instances of SQL Server 2005 - SP1 installed on one server. The default instance starts very slowly. When looking at the log I can see the delay is due to Resource Manager based upon the following error.
I have had my site running for several months now. My pages retrieve data from the SQL Server on the same machine. Today my users are are getting the message "SQL Server does not exist or access denied"
I have made sure that the credentials are correct. I can use those credentials to create a DSN on the server. So I don't know where to look for the problem. Help please!
Hi there!!! We got problem on sql server 2k, Sql server stops unknowingly, and all user database has marked as Suspect/Offline, and later on, after sql server stops, all user database has been detached. what is going on????
I have transactional replication set up between two dedicated servers. Server A is the PDC and Server B is a BDC (they are both Win2000 boxes). Both the servers are brand new, and replaced the two that were running like clock work (replication wise) for the last 12 months. I never had this problem with the old servers....
When the servers are shut down (as the case was a couple of weeks back with a power failure) or just recently when they were move to another room. Both servers boot up at the same time. Server B (which is the server holding the db being replicated) boots quicker and as a result replication fails and is then 'sucessfully stopped'. Unless I am aware of the server being rebooted and can monitor this potential problem, within 2 days the logfile grows to large and everything comes to a crashing halt.
I just remove replication, truncate and shrink the log, reset replication and we're away.... BUT I really need to know why it is happening in the first place. I figure there must be a setting that I have forgotten about or something.
Can anyone help me? My brand new installation of SQL Server 6.5 running on Windows 2000 suddenly stops working for about 6 minutes, in this periods no one can use SQL 6.5 services because it stops responding. My logs is show below:
2002/04/08 15:50:22.60 ods Error : 17832, Severity: 18, State: 0 2002/04/08 15:50:22.60 ods Unable to read login packet(s). 2002/04/08 15:50:24.50 ods Error : 17832, Severity: 18, State: 0 2002/04/08 15:50:24.50 ods Unable to read login packet(s). 2002/04/08 15:50:26.79 ods Error : 17832, Severity: 18, State: 0 2002/04/08 15:50:26.79 ods Unable to read login packet(s). 2002/04/09 07:10:21.48 ods Error : 17832, Severity: 18, State: 0 2002/04/09 07:10:21.48 ods Unable to read login packet(s). 2002/04/09 07:53:33.76 ods Error : 17824, Severity: 10, State: 0 2002/04/09 07:53:33.76 ods Unable to write to ListenOn connection '.pipesqlquery', loginname 'sa', hostname '2M_ROSANNA'. 2002/04/09 07:53:33.76 ods OS Error : 232, 2002/04/09 07:53:33.78 spid75 Error : 1608, Severity: 21, State: 2 2002/04/09 07:53:33.78 spid75 A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information. 2002/04/09 07:53:41.10 ods Error : 17824, Severity: 10, State: 0 2002/04/09 07:53:41.10 ods Unable to write to ListenOn connection '.pipesqlquery', loginname 'sa', hostname 'CE_SANDRA'. 2002/04/09 07:53:41.10 ods OS Error : 232, 2002/04/09 07:53:41.10 spid80 Error : 1608, Severity: 21, State: 2 2002/04/09 07:53:41.10 spid80 A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information. 2002/04/09 07:55:42.20 ods Error : 17824, Severity: 10, State: 0 2002/04/09 07:55:42.20 ods Unable to write to ListenOn connection '.pipesqlquery', loginname 'sa', hostname 'CE_SANDRA'. 2002/04/09 07:55:42.20 ods OS Error : 232, 2002/04/09 07:55:42.20 spid53 Error : 1608, Severity: 21, State: 2 2002/04/09 07:55:42.20 spid53 A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information. 2002/04/09 07:57:09.40 ods Error : 17824, Severity: 10, State: 0 2002/04/09 07:57:09.40 ods Unable to write to ListenOn connection '.pipesqlquery', loginname 'sa', hostname 'FE_FERTILIDAD'. 2002/04/09 07:57:09.40 ods OS Error : 232, 2002/04/09 07:57:09.40 spid91 Error : 1608, Severity: 21, State: 2 2002/04/09 07:57:09.40 spid91 A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information. 2002/04/09 07:57:09.40 ods Error : 17824, Severity: 10, State: 0 2002/04/09 07:57:09.40 ods Unable to write to ListenOn connection '.pipesqlquery', loginname 'sa', hostname 'SF_ROSA'. 2002/04/09 07:57:09.40 ods OS Error : 232, 2002/04/09 07:57:09.40 spid11 Error : 1608, Severity: 21, State: 2 2002/04/09 07:57:09.40 spid11 A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information. 2002/04/09 07:57:36.04 ods Error : 17824, Severity: 10, State: 0 2002/04/09 07:57:36.04 ods Unable to write to ListenOn connection '.pipesqlquery', loginname 'sa', hostname 'CE_MILAGROS'. 2002/04/09 07:57:36.04 ods OS Error : 232, 2002/04/09 07:57:36.04 spid60 Error : 1608, Severity: 21, State: 2 2002/04/09 07:57:36.04 spid60 A network error was encountered while sending results to the front end. Check the SQL Server errorlog for more information.
The problems begin on 2002/04/09 at 7:53am. and it respond again at 7:57, there's no need to restart the service.
Hi All, I am having exchange server 2003. With following details.
1.Operating System 2003 standerd with sp2. 2.Exchange server 2003. Service pack don't know ( How to check)
From last 2 months, every two days my exchange server stops responding to clients.
When I check the services, all the Exchange related services are ON. ( they are running fine).
Then I use to Restart All excahnge related services, i.e Microsoft Exchange Information Store & Ms Exchange System Attended service and things starts working fine again.
This I have to do every 2 days.
I don't know why this is happening.
Can anyone assist me to resolve as it is getting critical day-by-day. Also How can I check which service pack of exchange is installed.
when I run a package from a command window using dtexec, the job immediately says success. DTExec: The package execution returned DTSER_SUCCESS (0). Started: 3:37:41 PM Finished: 3:37:43 PM Elapsed: 2.719 seconds
However the Job is still in th agent and the status is executing. The implications of this are not good. Is this how the sql server agent job task is supposed to work by design.
I have a test server running both 2000 and 2005 Reporting Services. Each day I have to restart the Report Server Windows service for the 2005 Report Server. This is the error I get when I try to access the Report Manager
The Report Server Windows service 'ReportServer$TSQL4' is not running. The service must be running to use Report Server. (rsReportServerServiceUnavailable) Get Online Help
After I start the Report Server Windows service using the Report Services Configuration tool I can access the 2005 Report Manager without errors. The windows service start up type is set to automatic.
I can not find why the 2005 version keeps going down.
I'm using SQL server 2014 and all of a sudden the server stops working and I have to go to the configuration manager to start it. Though the start mode is set to automatic, this still happens and I just don't know why.
I was trying to migrate an ASP application from Access to SQL Server 2005 express, and found surprisingly that some code stops working which would seem to be independent of the data source. For example:
qtext = "SELECT MainText, TextType FROM MessageText WHERE [etc. etc. -- the query is OK]" rsMain.open qtext, dbcon, , , adCmdText if not (rsMain.BOF and rsMain.EOF) then
rsMain.MoveFirst do while not rsMain.EOF
select case rsMain.fields(1).value
case 1
session("headline") = rsMain.fields(0).value case 2
introtext = rsMain.fields(0).value case 6
helptext = rsMain.fields(0).value end select rsMain.MoveNext loop end if rsMain.Close
"rsMain" is an ADO recorset which defaults to a forward-only cursor as opened above; dbcon is an ADO database connection. Nothing fancy; and it has been working for years as expected with Access. But the recordset seems to behave differently when SQL Server is the data source (even though the whole point of ADO is to provide a level of abstraction, and I expected it not to change.) In the code above, checking the value of "rsMain.Fields(1).value" causes "rsMain.Fields(0).value" to disappear or become inaccessible. As a simple debug exercise, I tried response.writing "rsMain.Fields(0).value", a block of text, prior to the select case block, and it works fine once (as long as rsMain.Fields(1).value has not been accessed), but then a second write comes up empty.
Is it reasonable to expect that ADO recordsets and cursors function differently if SQL server is the data source vs. Access? Is this documented anywhere?
I have a report that uses three tables from a database. As long as I only use two of the tables, it runs fine. I need the data from the third table for a line chart. So of course there is a great deal of data in the third table. I have a where clause for start date and end date. Is there a way I could only search the third table after I know what I need from it? Or
We just moved source server to newer, bigger box ... Windows 2003 and Active Directory ... Snapshot agent worked but distribution failed ... Same login as on older machine, login is sysadm, used DCOMCNFG to allow ability to launch process ... What are we missing?
I am having a recurring issue that involves a stored proc using OPENROWSET to query an excel file. I used the surface area config to enable this on the server, and made sure that is still set. After an undetermined amount of time, the OPENROWSET query starts failing with this message:
OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" returned message "Unspecified error". Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)".
I corrected this previously by restarting the SQL server, but not before I checked permissions, the excel file itself, etc, and that was the last thing to try.
I am using SQL 2005 with SP1 installed - my primary approach to tackling this issue is to install the SP2, but I did not find this bug referenced in the fixes, and was wondering if anyone else had further insight.
I have never seen this error before... When I click on DTS to either open an existing package or create a new one I get the following errors: Error in the DLL, DTS Design Error. When I try to create a new DTS it gives me the errors but still opens but I'm missing all of the connection objects except for MS data link and other connection. I had no problems designing and executing the packages from a development box. I'm not even refering to the typical scheduling problems that exist when SQL Agent is configured incorrectly!
hi,guysi have query which given below output given belowmanager personlevel person name20851 Howard Wilson120852Howard Wilson220853Howard Wilson320854Howard Wilson420855Howard Wilson560861Andrew Saxon60862Andrew Saxon60863Ian Thompson60864Ian Thompson60865Phil Darganwhat i want is after a manager ends i want a null to be inserted foreach of there columnsso that i can distinguish that when a new manager startsso thatt output looks like thismanager personlevel person name20851 Howard Wilson120852Howard Wilson220853Howard Wilson320854Howard Wilson420855Howard Wilson5null null null60861Andrew Saxon60862Andrew Saxon60863Ian Thompson60864Ian Thompson60865Phil DarganBrlliant minds any solution for this..i know can i loop through the records and do itand check for a new managerbut i want a better solution ..give me your ideads folks..Regards,Navin Mahindroo
Hello, I€™m creating a cube with Analysis services 2000 and SQLServer 2000 that has the following structure: The fact table has a primary key and some measures:
Fact_Table
PKFact (the primary key) Measure 1 Measure 2
And I have some dimensions, but I€™ll put here the one of interest, this dimension has a foreign key to the fact_table, this is because it is really a €œdetail€? of the fact table, the interesting thing here is that this dimension not only has a foreign key to the fact_table, but also is a parent-child dimension:
Dimension_Table
FKFact (the foreign key to the €œPKFact€? field of the fact table) PKId (The id of the field for the parent-child relationship) FKParentId (the foreign key to this same table, this is, the parent of the field) TheLevel (the data€¦)
So, if I create the cube without the Dimension_Table (of course, I have more dimensions), the cube shows the data correctly, but when I include this dimension, the data of the fact_table starts to be repeated once for each row in the dimension table (once for each row that has the relation PKFact €“ FKFact of course), Somebody knows how I can avoid this data being repeated? I€™ve tried a lot of things but none works.. Please help!!
How would I write a query on a table containing a column of ints, where I want to retrieve the rows where that int value starts with a number? I know that you can do this with strings by using "....WHERE thisfield LIKE ('123%')", but if 'thisfield' is an int, how would I do this? Thanks!