Apache HTTP Server error: ‘An attempt was made to access a socket in a way forbidden by it’s access permissions. AH00072: make_sock: could not bind to address 0.0.0.0:80. AH00451: no listening sockets available, shutting down.’

I discovered that this error was caused by ‘SQL Server Express 2008 Reporting Services’ also using TCP Port 80. Apache HTTP Server also uses TCP Port 80 by default.

Fix: Reconfigure either your SQL Server Reporting Services or the Apache HTTP Server to use another port other than TCP Port 80.
Or you can temporarily stop the SQL Server Reporting Services service in order to continue using your Apache HTTP Server.

SQL Server Reporting Services
Note that the SSRS service can remain active even if you uninstall SQL Server. To stop the service:

  1. Open SQL Server Configuration Manager.
  2. Select “SQL Server Services” in the left-hand pane.
  3. Double-click “SQL Server Reporting Services”.
  4. Hit Stop.
  5. Switch to the Service tab and set the Start Mode to “Manual”.

    If this doesn’t fix your issue then it could be there’s another Windows program using TCP Port 80. You can find out by entering the following on the Windows command line:

    netstat -ao

    The active TCP addresses and ports will be listed. Look for the line where Local Address is “0.0.0.0:80″ and make note of the value in the PID column.

    Now start Task Manager. Navigate to the ‘Processes’ tab. If there’s no ‘PID’ column, click View > Select Columns… to ensure “PID (Process Identifier)” is checked. You can now locate the PID you made a note of above. The ‘Description’ and ‘Image Path’ properties should identify which application is using the port.

    Task Manager can allow you to kill the process, but be very cautious about doing that if it’s a System Process, such as “NT Kernel & System”.

Advertisements

Cannot connect to [database name]. 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 correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)

Server Name: Make sure you are typing server name (i.e. host name or computer name) correctly along with the proper instance name of an installed instance of SQL Server.

As, even using ‘(local)’ or ‘(localhost)’ can also cause this error:

Correct format is: Server-name\db-instance-name. e.g. Server01\SQLExpress2008

Also (if using Windows Authentication mode) make sure the format of the username is as follows: Server-name\User-name. e.g. Server01\Administrator

SQL SERVER – Error 7308: MS Jet OLEDB 4.0 cannot be used for distributed queries because the provider is configured to run in single-threaded apartment mode.

FIX suggestion (which works for me), by Mitch Stokely:

1. On 64-bit servers and boxes, you need to first UNINSTALL all 32-bit Microsoft Office applications and instances (Access 2007 install, Office 10 32-bit, etc.). If you dont, you cannot install the new 64-bit Microsoft Access Database Engine 2010 Redistributable components. Yes, its a headache but the only way I found to install the new replacements for the JET engine components that need to run on 64-bit machines.

2. Download and install the new component from Microsoft:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c06b8369-60dd-4b64-a44b-84b371ede16d&displaylang=en
* This will install the access and other engines you need to set up linked servers, OPENROWSET excel files, etc.

3. Open up SQL Server and run the following:

sp_configure ‘show advanced options’, 1;
GO
RECONFIGURE;
GO
sp_configure ‘Ad Hoc Distributed Queries’, 1;
GO
RECONFIGURE;
GO

EXEC master.dbo.sp_MSset_oledb_prop N’Microsoft.ACE.OLEDB.12.0′, N’AllowInProcess’, 1
GO
EXEC master.dbo.sp_MSset_oledb_prop N’Microsoft.ACE.OLEDB.12.0′, N’DynamicParameters’, 1
GO

* This sets the parameters needed to access and run queries related to the components.

4. Now, if you are running OPENROWSET calls you need to abandon calls made using the old JET parameters and use the new calls as follows:

(*Example, importing an EXCEL file directly into SQL):

DONT DO THIS….

SELECT * FROM OPENROWSET(‘Microsoft.Jet.OLEDB.4.0′,’Excel 8.0;HDR=YES;Database=c:\PATH_TO_YOUR_EXEXCEL_FILE.xls’,’select * from [sheet1$]‘)

USE THIS INSTEAD…

SELECT * FROM OPENROWSET(‘Microsoft.ACE.OLEDB.12.0′, ‘Excel 12.0;Database=c:\PATH_TO_YOUR_EXEXCEL_FILE.xls’,’select * from [sheet1$]‘)

*At this point resolved two SQL issues and ran perfectly

5. Now for the fun part…..find all your Office Disks and reinstall Office and/or applications needed back onto the machine. You can install the 64- bit version of Office 10 by going onto the disk and going into the 64-bit folder and running it but beware as in some cases some third party apps dont interface yet with that version of Office.

Hope that help!

Mitch Stokely – Texas
Chief Internet Architect

See original post on Pinal Dave’s blog here >>

Trying to install reporting services for Microsoft SQL server on Windows 7, but the option to install reporting services is disabled in the setup?

Before you install SQL Server 2005 Reporting Services, you must enable Microsoft ASP.NET and Microsoft Internet Information Services (IIS). To enable ASP.NET and IIS, follow these steps:

  1. In Control Panel, click Programs, and then double-click Programs and Features.
  2. In the User Account Control dialog box, click Continue.
  3. Click Turn Windows features on or off.
  4. In the Windows Features dialog box, expand Internet Information Services, expand Web Management Tools, expand IIS 6 Management Compatibility, and then click to select the following check boxes:
    • IIS 6 WMI Compatibility
    • IIS Metabase and IIS 6 configuration compatibility
  5. Expand World Wide Web Services, expand Application Development Features, and then click to select the following check boxes:
    • ASP.NET
    • ISAPI Extensions
    • ISAPI Filters
  6. Expand Common HTTP Features, and then click to select the following check boxes:
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • HTTP Redirection
    • Static Content
  7. Expand Security, and then click to select the Windows Authentication check box.

Note If you do not enable all these features, the Reporting Services option does not appear in the Feature Selection dialog box of the SQL Server Setup program.

support.microsoft.com – kb934164

The OLE DB provider “Microsoft.Jet.OLEDB.4.0” has not been registered.

Depending on your OS you could run odbcad32.exe on your SQL Server to bring up the Data Sources screen where you should be able to confirm what ODBC providers the server has installed (or not installed), as the case may be.


If you’re using 64bit, then this error most likely results from the fact 64-bit SQL Server cannot use Jet, as there is no 64-bit OLEDB provider for Jet.


I came across a possible word-around, which could be to execute the following script in MSSMS, and then restart the MSSQLSERVER service:

EXEC
sp_configure ‘show advanced options’, 1;
GO
RECONFIGURE
;
GO
EXEC
sp_configure ‘Ad Hoc Distributed Queries’, 1
GO
RECONFIGURE
;
GO

 

Additional help can be found on this .Net forum: http://www.sqlservercentral.com/forums/Topic445277-149-1.aspx

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 correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)

The reason that you may get this error message is the client stack could not receive SSRP response UDP packet from SQL Browser. The following steps may help to isolate the issue:

1) Make sure your server name is correct.
2) Make sure your instance name is correct and there is actually such an instance on your target machine. [Some application converts \\ to \. If you are not sure about your application, please try both Server\Instance and Server\\Instance in your connection string]
3) Make sure the server machine is reachable, e.g, DNS can be resolved correctly; you are able to ping the server.
4) Make sure SQL Browser service is running on the server.
5) If firewall is enabled on the server, you need to put sqlbrowser.exe and/or UDP port 1434 into exception.