SharePoint Fixed issues when stopped SENS service

Now I faced this solution many times now and for many problems that I faced so I decided that I would blog about all the issues that I faced and where solvable by this same solution.

The SENS service (or the System Event Notification Service) is designed for “Applications designed for use by mobile users require a unique set of connectivity functions and notifications. In the past these individual applications were required to implement these features internally. The System Event Notification Service (SENS) now provides these capabilities in the operating system, creating a uniform connectivity and notification interface for applications. Using SENS developers can determine connection bandwidth and latency information from within their application and optimize the application's operation based on those conditions.” (*)

So I will start with the solution for all the problems I faced and that was to stop this service by issuing the command:

net stop sens

Now the problems I faced and that are solvable by this solution are:

1. The explorer view of SharePoint lists was not working.
2. When you try to publish an InfoPath form it would keep telling you that the target URL is not valid.
3. Cannot connect to server when you try to access SharePoint data from MS-Office applications.

Now to be clear this would be only needed if you have SharePoint and Office client applications installed on the same machine, and hence it should never happen in production environments and so this solution would only be applicable for development/test environments as the office client applications would be running on other machines that do not have SharePoint installed on them.