Month: August 2010

WCF Publishing error

Server Error in ‘/generalservice’ Application.

The type ‘GeneralService.Service1’, provided as the Service attribute value in the ServiceHost directive, or provided in the configuration element system.serviceModel/ serviceHostingEnvironment/serviceActivations could not be found.

“generalservice” is the name of the application in IIS. I renamed Service1 into “GeneralService” and the implementing class into Maths. But when I publish the service to IIS, I got the error above. The issue was in the GeneralService.svc (that was earlier named as “Service1.svc”) the ServiceHost  service was still registered as

Service=”GeneralService.Service1″

Updated to Service=”GeneralService.Maths”. Issue Solved 🙂

Advertisement

IIS 7 Error when deploying ASP.Net Web Service

Error: “Handler “WebServiceHandlerFactory-Integrated” has a bad module “ManagedPipelineHandler” in its module list”

 

This error showed up when I tried to deploy an ASP.Net Web Service to IIS 7. I tried multiple thongs, including: adding Script Handlers, changing ports and what not.

But thanks to the post here, I just ran the following command and I was able to access the web service.

C:\Windows\Microsoft.NET\Framework\(version)>aspnet_regiis.exe –i

 

This command invokes the ASP.Net IIS Registration tool. Detailed here.

SQL Server 2008 Protocols

SQL Server 2008 supports 4 protocols using which a client can connect to the server. Their usage depends on the environment that the server is being used. The following protocols are available and a brief write up on what these are meant to do:

Shared Memory: This is the basic protocol that SQL Server 2008 supports and has no configurable settings. Considering that the clients using the Shared Memory protocol can connect only to a SQL Server instance running on the same computer, the usage of this protocol is pretty limited unless in  troubleshooting. Shared Memory protocol cannot be used by anyone using MDAC 2.8 or earlier and if such a connection is attempted, Named Pipes protocol is used instead.

Named Pipes: A protocol developed for local area networks (LANs). A portion of memory is used by one process to pass information to another process, so that the output of one is the input of the other. The second process can be local (on the same computer as the first) or remote (on a networked computer).

TCP/IP: Enabling SQL Server to use TCP/IP requires the most configuration effort, but most networked computers are already properly configured.

Virtual Interface Adapter (VIA): A protocol that works with VIA hardware. This is a specialized protocol.