Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

The remote procedure call failed with on MSSQL Server 2008

Tags:

sql-server

Recently, I have installed MSSQL Server 2008 Express.

Every time I try to enable "SQL Server Agent (SQLEXPRESS)", I got this error message:

WMI Provider Error: "The Remote procedure call failed".

I have tried to search for a solution but I have found some solutions and tried them all but It is still not working. Do you have know a good solution for this?

In addition, what is SQL Server Agent? do we really need it?

like image 837
olidev Avatar asked Oct 27 '11 17:10

olidev


People also ask

How do I fix the remote procedure call failed in SQL Server Configuration Manager?

Open command prompt under administrative privileges i.e., using “Run as Administrator” and run as shown in the snippet below. Now, you can go ahead and open SQL Server Services under SQL Server Configuration Manger to see all SQL Server Services.

How fix remote procedure call failed 0x800706be?

Solution: Install SQL Server 2008 R2 SP2, restart, open SQL Server Configuration Manager and ALL is good. I had the same problem described in the question, so I did a check for Windows Updates. It offered 'Microsoft SQL Server 2008 Service Pack 3', which fixed the issue after installing it. Yep!

Can T Remote connect to SQL Server?

Right-click on your server name and click 'Properties'. Go to the Security page for Server Authentication, and select 'SQL Server and Windows Authentication' mode. Then, go to the Connections page and ensure that "Allow remote connections to this server" is checked, and click OK.


1 Answers

This is a bit strange.
One of the restrictions of the free SQL Server Express (compared to the bigger editions) is that it has no SQL Server Agent.

So you shouldn't even be able try to enable SQL Server Agent, because your edition doesn't support it!

However, I have SQL Server 2008 Express installed as well, and I never cared to take a look if the SQL Server Agent service is listed on my machine.
I just looked on my machine: it is there, it's called "SQL Server Agent (SQLEXPRESS)" exactly as yours, and I'm even able to start it.
I didn't expect that!

But it's not visible in SQL Server Management Studio, so I can't create any jobs (and I expected that).
Apparently Microsoft restricted the use of SQL Server Agent in the Express edition not by omitting the service at all, but by making it invisible in Management Studio.

So my actual answer is this:
Don't waste time by trying to start SQL Server Agent.
You don't need it to run the database, and you can't use it anyway even if you can get it to run.

like image 73
Christian Specht Avatar answered Nov 04 '22 11:11

Christian Specht