When our rep distribution services time-out (several times a day) some dba's just restart the service while others restart the rep job which starts the service. Are there any differences between these two methods? Does restarting the service inherit any changes made to the job's attributes?
We have SQL 2000 (SP2) , Our SQL server agent showing green light as started from EM , It is succussfully restarting from NT Services too . But When I open the properties of the jobs from EM its gives error message SQL DMO error " SQl Agent is starting , try later " . And in EM Next run Date & Time not available .
MDDB database is accessable & in Log file its recovered fully
I installed SQL Server Studio MAnagement Express, and for some reason - I can't login to the server database engine. I try to enter '.SQL EXPRESS' in the 'connect to server' form, but keep getting error. I understand I have to start the service first, going into Start>All ProgramsMicrosoft SQL Server 2005>configuration Tools> -here I got nothing but 'SQL Server Error and Usage Reporting'... I assume something is missing here for controling the server, correct ?
I installed SQL Server 2005 on Windows 2000 SP4 Machine. All services except the Reporting Service is running in the PC. On trying to start the service a message saying "Could not Start reporting Service. No error reported....." Uninstalled SQL Server2005 and installed again. At present no service pack installed. Please Help
I wonder if you can help me with a problem I have trying to support a web based application that uses SQL 2005.
The problem is that the application developers tell me that it is neccessary to stop and restart the SQL service as part of the troubleshooting process when their application stops working. Unfortunately, the customer has our application database on a clustered SQL instance that is used by other applications so they cannot just stop and restart the SQL service because this will have a major impact on all the other instances...
Is there another way that would effectively do the same thing as stopping and restarting the SQL service? I have read that dettaching and re-attaching might do the same but application developers say onlt stopping/restarting services is sufficient to break the connection with the application.
Any advice would be really welcome as I am completely new to SQL and struggling with this!
Folks,We're implementing a software based mirroring solution. This solutionrequires that the SQL Server service on the target server be stoppedwhile data is being replicated from the source server.One problem we encountered while testing was that the SQL ServerService on the target server was inadvertantly started when usersselected that server in Enterprise Manager. Is there any way to keepthe service from starting through Enterprise Manager?Thanks
Please feel free to redirect me if this has been previously addressed. I've read through the FAQ post and searched the forums, and as yet haven't found anything relevant on Google so I'm hoping you folks can help.
I am using SQL Server 2005 Express Edition on a fully patched Windows 2000 Server, and for some reason the database just will not start up when the machine starts or reboots. The service starts fine if I go start it by hand though. This is obnoxious because it prevents me from running fully automated updates to the box since that reboots it at least once a week on "patch Tuesday".
Here are what my related services and their startup types look like:
SQL Server (MSSQLSERVER) Automatic SQL Server Active Directory Helper Disabled SQL Server Browser Disabled SQL Server VSS Writer Manual
This is a production machine so I'd prefer not to run any services I don't have to. All this database needs to do is sit there and get hit by a local Cold Fusion instance that talks to it by TCP/IP. Any administration on it I tend to do locally with Management Studio Express by remotely logging into the server on it's internal IP.
The really weird thing is, I have these services configured exactly the same on development environments I've created in Windows XP and Windows 2003 Server Standard Edition. This seems to be specific to Windows 2000 Server, and I just can't figure it out...
I'm not sure i was clear the first time. When the MSSQLServer Service is stopped and started, it stops the SQLServerAgent Service also. But when the MSSQLServer Service is started, it DOES NOT start the SQLServerAgent Service. I don't think this is configurable, so I was wondering if someone had a workaround (.bat file, service dependency, etc.).
Hello there,This is a bit of strange one.My local version of SQL Server fails to start when I boot yet if Istart Enterprise Manager its started and working fine. ISQL or QueryAnalyzer is also not working.If I try and register the server by another SQL Server is not there. Methinks that the named pipes might be a bit broken but would appreciateany advise from people.ThanksGinters
I installed SQL Server 2005 Integration services on Windows XP machine. Then I went to the SQL Server Configuration Manager and tried to Start the SSIS service. The "Log On As" value is "NT AUTHORITYNetworkService". But I get the follwoing error:
The request failed or the service did not respond in a timely fashion. COnsult the event log or other applicable error logs for details.
Event Log details: ------------------ The SQL Server Integration Services service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I tried running the service using the "Local Service" and the "Local System" accounts also, but am still encountering the same error. What do I do...
We have windows server 2000 and sql server 2005 on the same machine with 15 clients. There was a power failure. The sql server is automatically stopped. When we tried to start the service we are getting the error as action failed please check application event log for errors.
This has happened for the 2 times, kindly tell me why this happens and what precaution we can take and is there any setting we are missing. Since I am newbie to sql server and windows server I am unable to solve this problem.
After the install is done I start the service form the command prompt using
start mssqlserver
I see that the SQL Server service has started under NETWORK SERVICE account!!! when the documentation i Read on MSDN says it starts in Local System account
I have a Win 2003 server running 3 instances of SQL 2000 Enterprise. The problem is I can only start 2 of the 3 Job Agents at a time, as the 3rd gets stuck in a starting state. Has anyone struck this problem before?
One server, a part of a 2 node always on cluster, had problems, I had to restart.
I'm getting this error for example now:
Error: 49910, Severity: 10, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. + SQL Server was unable to run a new system task, either because there is insufficient memory or the number of configured sessions exceeds the maximum allowed in the server. Verify that the server has adequate memory. Use sp_configure with option 'user connections' to check the maximum number of user connections allowed. Use sys.dm_exec_sessions to check the current number of sessions, including user processes.
Now, on the instance I have activated maximum servere memory, my question; Is it possible to adjust this setting without starting the service?
Hi, I've been trying for the past week to get SQL 2005 Server up and running.The SQL is up and running however I am unable to get the Reporting service to start. The log file is below but the main line is:
ReportingServicesService!library!4!29/06/2006-14:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'VIDICOMASPNET' is not recognized., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException:The user or group name 'VIDICOMASPNET' is not recognized.
But the domain user ASPNET is present. Similar posts across the internet mention about the .NET Framework not be installed correctly. I have reinstalled it many times.
Any help is most appreciated.
Tom
Here is the full log file: <Header> <Product>Microsoft SQL Server Reporting Services Version 9.00.1399.00</Product> <Locale>en-US</Locale> <TimeZone>GMT Daylight Time</TimeZone> <Path>C:Program FilesMicrosoft SQL ServerMSSQL.4Reporting ServicesLogFilesReportServerService__main_06_29_2006_14_33_39.log</Path> <SystemName>CRM</SystemName> <OSName>Microsoft Windows NT 5.0.2195 Service Pack 4</OSName> <OSVersion>5.0.2195.262144</OSVersion></Header>ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing ConnectionType to '1' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.ReportingServicesService!library!4!29/06/2006-14:33:41:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.ReportingServicesService!servicecontroller!9!29/06/2006-14:33:45:: Total Physical memory: 267894784ReportingServicesService!library!4!29/06/2006-14:33:45:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'VIDICOMASPNET' is not recognized., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'VIDICOMASPNET' is not recognized.ReportingServicesService!servicecontroller!4!29/06/2006-14:33:47:: e ERROR: Exception caught starting RPC server: Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'VIDICOMASPNET' is not recognized. at Microsoft.ReportingServices.Library.Native.NameToSid(String name) at Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServer(Boolean firstTime)
i cannot seem to get rid of this error. My page works in other functions that have the same syntax and format. just this one doesnt. i tried changing the format but still the same thing. SQL DB is DateTime. Any Suggestions?
Function UpdateException(ByVal qID As String, ByVal exception_Status As String, ByVal completed As String, byval notes as string, byVal Username as string) As Integer dim strDate as date = datetime.now() dim strdate1 as string = strDate.tostring("MM-dd-yy") Dim connectionString As String = "server='servername'; trusted_connection=true; Database='CPD_Reports'" Dim sqlConnection As System.Data.SqlClient.SqlConnection = New System.Data.SqlClient.SqlConnection(connectionString)
Dim queryString As String = "UPDATE [Master_CPD_Reports] SET [Exception_Status]=@Exception_Status, [Completed]"& _ "= @Completed, [Completion_Date]= @Completion_Date, [Username]= @Username WHERE ([Master_CPD_Reports].[QID] = @QID)" Dim sqlCommand As System.Data.SqlClient.SqlCommand = New System.Data.SqlClient.SqlCommand(queryString, sqlConnection)
sqlCommand.Parameters.Add("@QID", System.Data.SqlDbType.VarChar).Value = qID sqlCommand.Parameters.Add("@Exception_Status", System.Data.SqlDbType.VarChar).Value = exception_Status sqlCommand.Parameters.Add("@Completed", System.Data.SqlDbType.VarChar).Value = completed sqlCommand.Parameters.Add("@Completion_Date", System.Data.SqlDbType.varchar).Value = strDate1 sqlCommand.Parameters.Add("@Username", System.Data.SqlDbType.DateTime).Value = UserName dim NotesUpdate as string = "INSERT INTO [CPD_Notes] ([qID], [Notes], [Notes_Date], [Username]) VALUES (@qID, @notes, @Date, @UserName1)" Dim sqlCommand1 As System.Data.SqlClient.SqlCommand = New System.Data.SqlClient.SqlCommand(NotesUpdate, sqlConnection) sqlcommand1.parameters.add("@qID", system.data.sqldbtype.varchar).value = qID sqlcommand1.parameters.add("@Notes", system.data.sqldbtype.varchar).value = notes sqlcommand1.parameters.add("@UserName1", system.data.sqldbtype.varchar).value = Username sqlcommand1.parameters.add("@Date", system.data.sqldbtype.datetime).value = DateTime.now() Dim rowsAffected As Integer = 0 trace.warn(strdate1)
sqlConnection.Open Try rowsAffected = sqlCommand.ExecuteNonQuery Finally End Try
I upgraded my SQL 2005 Workgroup 2005 to SP2 and subsequently could not get the SQL Server service running. Turns out this was a problem because I had created separate folders for my data and log files. The distmdl.mdf and mssqlsystemresource.mdf files were in my data folder and distmdl.ldf and mssqlsystemresource.ldf were in my log folder. During SP2 upgrade a new distmdl.ldf and mssqlsystemresource.ldf were created in my data folder. I deleted the distmdl.ldf and mssqlsystemresource.ldf files in my log folder and then moved the newly created ones in my data folder into the log folder and all is well now.
I have several DTS jobs that runs well as a job with my nt login account for the SQL agent service startup account, but if I use the System account they fail with this error. " Error opening datafile: Access is denied. Error source: Microsoft Data Transformation Services Flat File Rowset Provider"
The data has change access to the System account under the NT security.
We're using Reporting Services for lots of different reports at the moment. Some of these reports are quite big with thousands of pages. To speed them up I'd prefer using snapshots, but if I do so, it is necessary to defined a default-set of report parameters.
Unfortunately most of the reports parameters are query based, therefore I cannot choose a default parameter set for startup. If I start one of my reports it always displays the whole bunch of data and it is rendered immediately after clicking the link.
I have two ideas how this problem can be solved, but I don't know if MSSQL Reporting Services supports my ideas
1) Suppress automatic rendering on report startup somehow. Is it possible to set a parameter somewhere to suppress this "feature" ?
2) Use query based parameters to limit the default startup parameters to only a subset of the available data
I've read frequently how stored procedures we create shouldn't be named withsp_ since SQL Server will first check the master db before the current dbwhen trying to find the sp to execute. I always nodded and thought how Iwas glad I hadn't done that. For some reason it never clicked that UDFbehavior could be the same.I have several UDFs that start fn_... When I reference a UDF as dbo.fn_...does SQL Server check the master db for these and only upon not finding themcheck the current db? If so, is there a performance hit for this?TIA,John
I'm quite new to this forum. I've a fair experience in Databases and Programming. Now that I want to take a stride into Data Mining and Warehousing. Experts please suggest me where I can start from and any learning path ?
I am just starting out on SSIS, and have the following business challenge that I would like to solve utilizing SSIS. There are two SQL Server data stores, one would be the source, and other would be the destination. I need to grab some data from store 1, and insert that data into store 2. Here are my questions:
1) Before i move the data to store 2, i have to check some criterias by callin some sps, and then the end result would need to be inserted into the destination database. Can anyone tell me how would i setup the control flow, to accomodate that in SSIS?
2) Can someone email me a sample package that does something similar?
I just need a starting point so i can build the design of my package. Basically i need to call three sps during the process to move data. First one will compile a list of all the records to process. Second one, will pick those up, make some calls to set some other parameters, and then finally insert it into some staging tables. Third one should simply pick up the data from staging tables, to a replica of those tables in the actual destination db. I would really appreciate if I can get some response to this post soon. Also, I would appreciate if you can point me in the right direction in terms of how to design this using SSIS. Basically i need a starting point control flow design(rough) to understand what control flow items would be used in this case. Thanks.
The SQLAgent service was modified to login as a domain account. SQLAgent would not start. I made sure that the account was in the Admin group on the server, I setup the account as a System Administrator in SQL. I made sure that the network protocols in Client Network Utiliity and Server Network Utility where the same as other servers using the domain account. The message I'm getting is...
SQLServerAgent could not be started (reason: Unable to connect to server; SQLServerAgent cannot start).
I modified the properties for SQLAgent back to login as local account and I still get the same problem.
When my system re-boots SQLServerAgent will no longer start. The following message is sent to the NT Event Log:
(Event ID 103) "SQLServerAgent could not be started (reason: Unable to connect to server; SQLServerAgent cannot start)."
Following this message are two messages from MSSQLServer that read:
(Event ID 19020) "RPC Net-Library listening on: ncalrpc:USBGRSYSTST1[WMSG0000009A.00000001]."
So is this a timing issues? Is MSSQLServer taking too long to completely start before SQLServerAgent is started? If so, is there a way (without hacking through the registry) to make the SQLServerAgent service dependant on the MSSQLServer service?
This startup issue did not exist until an application was installed on the machine that also has several services that auto-start. I noticed that many of these new services are starting at the same time the MSSQLServer service is starting.
For three months I have be starting the SQL Agent using the following bat file
EXEC XP_CMDSHELL 'NET START SQLSERVERAGENT'.
Starting this week the agent is not starting. This is the error message
10/26/00 6:25:36 PM - ! [000] Password verification of the 'SQLAgentCmdExec' proxy account failed (reason: A required privilege is not held by the client)
I've installed sql server 7.0 on winnt. Later i've changed my system name. Due to this SQL SERVER is not running and i'm getting the following error. "Your SQL Server installation is either corrupt or has been tampered with (unkown package id). Please rerun setup.". I've changed my system name back to the original one and sql server is running again.
Is there any way to change my system name and sql server running??
I am using MS SQL 6.5 SP5, NT4.0. running Tivoli Service Desk. Two of the four agents on the Applications server were not running so I recycled the server and now NONE of the agents are coming up. Generally the agents show up on the application server control panel but they have not started. The status of the server is 'initializing' and the Watchdog has started but only the 'dispatcher'started. I have hard booted the aps server and recycled the aps and db servers both. I know that there is a way to suspend the agents but that has not been done and the 'resume' button is not available to use. I tried restarting the dispatcher but it didn't do anything. I have also gone into 'config' on the control panel and it shows that '4' agents are set to start up.
We run a Web version also so I have my help desk analysts using it but they cannot refer back to tickets that they have just opened, etc.
ANY SUGGESTIONS - I have been waiting on Tivoli to call me back for almost an hour and a half.
My SQL server is not sarting, Its giving me an error 2140 - An internal Windows NT error occured. I checked the Microsoft site found an article ran all the options to check if it works but invain.
I am stuck, its a production DB i have to get it up and running in the next hour
SQL 2000 was run in Windows NT4 under non-system account. If this account belongs Administrator's group then SQL Server starts successfully otherwise the error message "NETLIB SuperSocket info: Failed to get Exclusive port use(MSAFD Tcpip [TCP/IP]) : Error 10013. " is displayed. Could you please help me to solve the problem.
The SQLAgent service was modified to login as a domain account. SQLAgent would not start. I made sure that the account was in the Admin group on the server, I setup the account as a System Administrator in SQL. I made sure that the network protocols in Client Network Utiliity and Server Network Utility where the same as other servers using the domain account. The message I'm getting is...
SQLServerAgent could not be started (reason: Unable to connect to server; SQLServerAgent cannot start).
I modified the properties for SQLAgent back to login as local account and I still get the same problem.