Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am trying to set up the SQL Server Agent on our test server running with windows Small Business Server 2011 Standard and SQL Server 2008 R2 RTM. The Sql Server Agent node is not displayed in Sql management studio.
Here is what I know according to forums I read:
in services.msc, I have two Sql Server Agent (Sharepoint and SBSMonitoring) set as automatic. If I try to start the service, the following warning comes up: The SQL Server Agent service on Local Computer started and then stopped. Some services stop automically if they are not in use by other services or programs
in SQL Server Configuration Manager, under SQL Server Services, I have an error "The remote procedure call failed [0x800706be]". Under SQL Server Network Configuration (32bit), nothing is listed.
in Local Security Policy, Security Settings -> Local Policies -> User Rights Assignement: their is no Sql Server Agent Listed
in Sql Server Management Studio I created a new user with all the rights possible and after I logged with this user, Sql Server Agent was not showing
I did the following command mofcomp c:\program files (x86) \Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof" but it did not change the error "The remote procedure call failed" in SQL Server Services
Does anyone have a solution according to these facts?
Thank you
select serverproperty('edition') returns Express edition.
As confirmed you are using an Express edition.
There is no way to get SQL Server Agent on this.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
I have a problem. I can't start SQL Server 2014.
It's ok when I connect to a server as a Windows authentication, but when I try to connect as SQL Server authentication with username sa and my password, O get a SQL Server error 18456.
Why? When installing Management Studio with youtube video, there were few differences:
When installing new instance SQLExpress, there was error because the instance with this name already existed so I changed the name of instance to MSSQLServer...
Also in SQL Server Configuration Manager in SQL Server Services,there are 5 services and I think there shouldn't be so many:
Each SQL Server instance has their own services for different usages. Here you've 2 instances {"SQLEXPRESS", "MSSQLSERVER"}, each has its own SQL Agent. This is normal.
... but when I try to connect as SQL Server authentication with username sa and my password, O get a SQL Server error 18456. Why?
If you want to connect with system administrator account sa, you need to enable the mixed running mode of the target SQL Server instance, e.g. SQLEXPRESS. Because sa is not windows authentication. You've 2 options:
Enable this mixed running mode during the installation. Choose Windows Authentication and SQL Server Authentication.
Connect to your SQL Server instance with an adminstrator account using Windows Authentication and then change the server running mode.
If the server is already running on mixed mode, but you're still getting the same error. Then you're probably using a wrong password for sa. Did you use your windows password by mistake?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I have a windows server 2012 R1 Enterprise that my colleague set up in a virtualized environment, the host PC is no not domain joined, but the virtual environment is.
The issue is for some reason that server is not able to connect to SQL servers within the domain network. I've enabled IP/firewall and I can connect to the SQL server from all the other non-virtual machines, so, I don't think it's to do anything with the SQL
It's just that hyper-v environment that I'm having issues with. I cannot even connect using the excel, it simply says "SQL Server does not exist or access denied." Anyone else experienced the same issue?
here is the error message I get trying to connect to one of SQL servers.
"A network-related or instance-specific error occurred while establishing a connection to SQL server. The server was not found or was not accessible. Verify that the instance name is corrrect and that SQL server is configured to allow remote connection. (Provider: Named Pipes Provider, Error: 40-Could not open a connection to SQL server) (Microsoft SQL Server, Error:5) --> Access is denied
thanks
Normally the order and types of protocols used to connect to sql server are configured when sql server is installed. the order and priority of which can be used to influence the default connection protocol when using SQL server management studio The error
(Provider: Named Pipes Provider, Error: 40-Could not open a connection to SQL server) (Microsoft SQL Server, Error:5) --> Access is denied"
Indicates that the protocol on the SQL server that the SQL server management studio is requested is either
Blocked by the firewall on the inbound or outbound machine
Or the protocol is not enabled
The connection protocol default can be overridden by selecting the connection properties tab and selecting another protocol choice other than default.
to see what default is configured for (on the server that sql studio is installed on" run the following query against the master database
SELECT net_transport
FROM sys.dm_exec_connections
WHERE session_id = ##SPID;
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
I am very new to TFS and SharePoint so I hope I can explain myself as best as possible.
We currently run a single server farm that runs on Windows 2007 Standard, SQL 2008, TFS 2010 and SharePoint 3.0. I have been given the fun task of upgrading this to TFS 2012 and SharePoint 2010!
Now I have been following the steps that Microsoft provide but I am still hitting problems along the way and need to know the best possible approach!
I have built a new server with all TFS & SharePoint requirements. Windows 2008 R2, SQL 2008 R2. I have also installed TFS and SharePoint 2010. Before I configure anything I then used TFS backup and restore tools provided with the new installation to back up the existing Database on the old server and restored the databases onto the new server running SQL 2008 R2.
Before backing up the databases I made sure I have a backup of the report server encryption key. When trying to restore this I have the following problem?
Microsoft.ReportingServices.WmiProvider.WMIProviderException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. (rsReportServerDatabaseUnavailable)
Have I missed any steps for the upgrade?
Also when performing this upgrade, is there any chance of this interrupting our current TFS & SharePoint production server?
It sounds like you selected "Install but do not configure" when installing Reporting Services. For TFS 2010+ you need to have it configured as the TFS install will not do that for you like it used to in 2005/2008.
I have a blog post that includes how to configure RS: http://nakedalm.com/integrate-reporting-and-analyses-services-with-team-foundation-server-2013/
Although this is for 2013 it applies equally to 2012.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking for code must demonstrate a minimal understanding of the problem being solved. Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist
Closed 9 years ago.
Improve this question
I have a server with SQL Management Studio 2005 installed on a server 10.x.x.x as IP.
I also have a PC with SQL Management Studio 2005 Express installed.
The problem is that from my PC I can connect to the server successfully but I cannot to localhost even with Windows Authentication..
I tried to troubleshoot the problem but I couldn't find any SQL service in windows services.
also I don't know the credentials of the SQL specially that I was not asked to submit it during the SQL Management Studio 2005 Express Setup , any help please?
Management studio is just the tool to manage SQL databases. Hence the name. It is not the SQL Server itself.
If there's no SQL server service in services, chances are SQL Server is not installed.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I've just installed SQL Server 2012 and open the SQL Server Management Studio and when I try to login this problem occurs:
Can't connect to .....
My question is how can I know what is the server name?
And when I go to the SQL Server Configuration Manager I can't find the SQL Server services which should exist !!
Any answer ?
Thanks.
If you installed SQL Express, the correct server name is:
127.0.0.1\SQLEXPRESS
or
YOURMACHINENAME\SQLEXPRESS
If that does not work there are some steps you can take:
Check if the "SQL Server Browser" windows service is activated and running:
Go to Control Panel -> Administrative Tools -> Services
Open "SQL Server Browser" service and enable it (make it manual or automatic, depending on your needs)
Start it.
If that too does not work, you can also check if the TCP/IP protocol is enabled in your SQL Server instance. Follow these steps (tested for SS2012) to make sure:
Open "Sql Server Configuration Manager" in "Start Menu\Programs\Microsoft SQL Server 2012\Configuration Tools\"
Expand "SQL Server Network Configuration"
Go in "Protocols for <YourInstance>"
Enable TCP/IP
If you have any problem, check this blog post for details, as it contains screenshots and much more info.
That's it.