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 ?
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?
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
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 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.
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'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.
I have an almost virgin install of SQLExpres running on a WIN2K Pro system.
Have been able to create and connect db to Access 2000 without problem.
Now I wish to extend to remote connections. Using Surface Area Configuration tool, I changed Remote Connections to Local and Remote.
Whenever this setting contains TCP/IP and I try to restart the service I receive the following errors:
System Log:
The SQL Server (SQLEXPRESS) service terminated with service-specific error 10013.
Application Log:
Server TCP provider failed to listen on [ 'any' <ipv4> 0]. Tcp port is already in use.
TDSSNIClient initialization failed with error 0x271d, status code 0xa.
TDSSNIClient initialization failed with error 0x271d, status code 0x1.
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
If I change back to Local Connections Only or Local and Remote using named pipes only, the service starts up again without a problem.
After five days of investigating, researching, reinstalling and waiting I have to ask for help.
I have a VM with SP2013 and SQL Server 2012 SP1. I have installed the powerpivot plugin SP1.But when I run the PowerPivot for SharePoint 2013 configuration tool.
Hello! I have the following problem. I developed CLR Stored Procedure "StartNotification" and deploy it on db. This sp calls external web service. Furthermore, this sp is called according with SQL Server Agent Job's schedule. On my PC SQL Server works under Local System account and this web service is called correctly (Executed as user: NT AUTHORITYSYSTEM). But on ther other server the following exception is raised during job running: Date 17.04.2007 16:42:10 Log Job History (FailureNotificationJob)
Step ID 1 Server MSK-CDBPO-01 Job Name FailureNotificationJob Step Name MainStep Duration 00:00:00 Sql Severity 16 Sql Message ID 6522 Operator Emailed Operator Net sent Operator Paged Retries Attempted 0
Message Executed as user: CORPmssqlserver. A .NET Framework error occurred during execution of user defined routine or aggregate 'StartNotification': System.Security.SecurityException: Request for the permission of type 'System.Net.WebPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed. System.Security.SecurityException: at System.Security.CodeAccessSecurityEngine.Check(Object demand, StackCrawlMark& stackMark, Boolean isPermSet) at System.Security.CodeAccessPermission.Demand() at System.Net. The step failed.
What is the reason of this behaviour? Unfortunately I do not have direct access to this server. I have the following guesses: 1) CORPmssqlserver may have not enough permissions to call web service 2) Something wrong with SQL Server account's permissions 2) Something wrong with SQL Server Agent account's permissions I will take the will for the deed. Thanks.
We are using the whole BI-package from Microsoft - from SQL, DTS-package,Raporting Service and Analyze Service.
It should be very helpful to be able to create a metadata databases where you could find all releations between different objects (tables,views,reports,cubes,DTS-package,Databases.
Just to get answer for: 'where is view xxx used', 'what are Report xxx depending upon'.
While everything exists in different SQL databases it should possible to do.
I have a initiator and a target service broker peer.
Both are controlled by a C# unit test. The initiator uses the Microsoft.Samples.SqlServer class. The target service uses stored procedure activation.
Sending a message from the initiator to the target, saves the content of the message, along with its conversation handle in the target's database specific table.
The unit test needs - at a later time - to instruct the target to send a message back on the same conversation handle to the initiator service.
For this the C# unit test creates a Conversation off of the saved conversation handle:
Service client = new Service("cleintservicename", conn, tran);
Conversation dialog = null;
dialog = new Conversation(client, convHandle); Sending the message on this dialog generates an error "Message body: <Error xmlns="http://schemas.microsoft.com/SQL/ServiceBroker/Error"><Code>-8495</Code><Description>The conversation has already been acknowledged by another instance of this service.</Description></Error>". Is the error due to the fact that a service - using the activated stored procedure already picked up the conversation, so that a new reference to the service can not be created through the Service class in CLR? If so, I might need then to skip the activated stored procedure in favor or a CLR service, alltogether? Any help - greatly appreciated.
We seem to be being plagued by the error below by our SQL Server agent. This happens almost everytime we restart the server that has been running for a day or two.
Our SQL Server Agent uses a none expiring domain credential. I understand that this problem only happens when the profile being used by the SQL Servr Agent has changed (password change). What puzzles me is that the login is A ok and no changes has been made to it's password.
We always resolve this problem by changing the login used in the SQL Server Agent to local and after that, returning it back to it's original domain login. Unfortunately, we cant always do this everytime something goes wrong.
Can anyone please help us shed a light on this? We're using SQL2k with SP3a. Thanks!
Error:
An error 1069 - )The service did not start due to logon failure) occurred while performing this service operation on the SQLServerAgent service.
I am trying to send a message between to SQL Server 2005 instances on two different machines. I have checked all my routes and all my objects appear to be setup correctly. However, when running Profiler on the target machine, I receive the "This message has been dropped because the TO service could not be found. Service name: "[tcp://mydomain.com/TARGET/MyService]". Message origin: "Transport". This is my activated stored procedure that is sending the message to the target service. I am using certificate security. Any help appreciated....
CREATE PROCEDURE [usp_ProcessMessage]
AS
BEGIN
SET NOCOUNT ON;
DECLARE @conversation_handle uniqueidentifier
DECLARE @message_body AS VARBINARY(MAX)
WHILE (1=1)
BEGIN
BEGIN TRANSACTION;
WAITFOR(RECEIVE TOP (1)
@conversation_handle = conversation_handle,
@message_body = message_body
FROM [tcp://mydomain.com/INITIATE/MyQueue]
), TIMEOUT 1000;
IF (@@ROWCOUNT = 0)
BEGIN
COMMIT;
BREAK;
END
END CONVERSATION @conversation_handle
IF @message_body IS NOT NULL
BEGIN
BEGIN DIALOG CONVERSATION @conversation_handle
FROM SERVICE [tcp://mydomain.com/INITIATE/MyService]
TO SERVICE '[tcp://mydomain.com/TARGET/MyService]'
ON CONTRACT [tcp://mydomain.com/INITIATE/MyMessage/v1.0]
WITH ENCRYPTION = ON, LIFETIME = 600;
SEND ON CONVERSATION @conversation_handle
MESSAGE TYPE [tcp://mydomain.com/TARGET/VisitMessage]
(@message_body);
END
COMMIT;
END
END
GO
My endpoints are created like so:
CREATE ENDPOINT MyEndpoint
STATE = STARTED
AS TCP
(
LISTENER_PORT = 4022
)
FOR SERVICE_BROKER (AUTHENTICATION = CERTIFICATE MasterCertificate)
GO
GRANT CONNECT TO CertOwner
GRANT CONNECT ON ENDPOINT::MyEndpoint TO CertOwner
GO
And my routes like so:
GRANT SEND ON SERVICE::[tcp://mydomain.com/INITIATE/MyService] TO CertOwner
GO
CREATE REMOTE SERVICE BINDING [MyCertificateBinding]
TO SERVICE '[tcp://mydomain.com/TARGET/MyService]'
I have configured an instance to use static port, say 1435, and I turned off the Browser service.
I would like to know if I can use SSMSE to connect to the instance database directly. The instance is listening at port 1435 and accepting connection requests from other methods.
What I need to put into the "Server name: " field?
Normally, it would be like: <serverIP><InstanceID> with Browser turned on.
Now how do I add the port information to it, I tried
I am looking at implementing some sort of throttling whereby "expensive" reports are setup as Subscriptions (and hence are run by the Windows Service), while all other requests go the Web Service.
My question is:
Do the two systems share any underlying systems? I understand (of course) that they use the same DB, etc. etc. However, I can't quite tell whether there is an underlying engine that is a common base or if they really just spin up different instances of the same objects and essentially each host the application separately?
I am currently hardening our SQL 2012 (with AlwaysOn Availability Groups) environment. Both the SQL service and agent account are using service accounts (only domain user). SQL browser service is disabled. Permissions to all roles are handled by using domain groups.
Currently a lot of (default) NT Service accounts are listed (some with sysadmin privileges). Are there accounts that can be removed?
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.
