“Network mapping is disabled by default on domain networks. Your network administrator can use Group Policy to enable mapping.”

FIX:
Open up a command prompt with elevated privileges:
From the elevated command prompt, run the command "gpedit.msc" (no quotes). This will start the group policy editor with Administrator privileges for the local machine.

Inside of the Group Policy Object Editor, navigate the tree to Local Computer Policy -> Computer Configuration -> Administrative Templates -> Network -> Link-Layer Topology Discovery.

Once you are in the Link-Layer Topology Discovery section of the editor, simply Right-click and open properties for "Turn on Mapper I/O (LLTDIO) driver" and set it to Enabled, and also tick the "Allow operation while in domain" option.


Network domain administrators who want to enable the Network Map across a group of machines should follow these same instructions and, additionally, link the policy to the desired Active Directory container.

How to write Good Code?

http://xkcd.com/844/

System.Data.SqlClient.SqlException: Login failed for user '(username)'.

The first thing to check is whether the SQL Server is configured to use Mixed Mode Authentication or Integrated Authentication.

To do that, perform the following steps :-

1. Click Start - Programs - Microsoft SQL Server - Enterprise Manager to open the Enterprise Manager.
2. Connect to the appropriate Server if the SQL is a client installation.
3. Right click on the Server Node and click on Properties.
4. This opens the Properties Dialog.
5. Switch to the Security Tab.
6. Under the Security section, make sure the Option SQL Server and Windows is selected.
7. This ensures that your SQL Server is running under Mixed Mode Authentication.

The Next step is to ensure that the ASPNET account (IIS_WPG in case of Windows server 2003) has the appropriate access to the Database.

To do that, perform the following steps:

1. Open SQL Server Enterprise Manager (Start - Programs - Microsoft SQL Server - Enterprise Manager), select the appropriate server, and expand the Security folder.
2. In the Logins check whether the IIS_WPG is listed.
3. If it is not listed, right-click on Logins and select New Login
4. In the Name: textbox either enter [Server/Domain Name]\IIS_WPG or click on the ellipses button to open the Windows NT user/group picker.
5. Select the current machine’s IIS_WPG group and click Add and OK to close the picker. 
6. You then need to also set the default database and the permissions to access the database. To set the default database choose from the drop down list,
7. Next, click on the Database Access tab and specify the permissions.
8. Click on the Permit checkbox for every database that you wish to allow access to. You will also need to select database roles, checking db_owner will ensure your login has all necessary permissions to manage and use the selected database. 
9. Click OK to exit the property dialog. 

Your ASP.NET application is now configured to support integrated SQL Server authentication. 

http://www.eggheadcafe.com/community/aspnet/13/10190575/login-failed-for-user.aspx.

CuteFTP 8.0 pro, Socket Error 10054

Fix: Check to make sure FTP Service is Started on the VPS Server. Then , for additional info see: http://kb.globalscape.com/KnowledgebaseArticle10235.aspx

Sys.WebForms.PageRequestManagerServerErrorException: An unspecified error occurred.

You may experience this error if you're using an update Panel on an aspx page within an AJAX enabled web site.

This tutorial on the MSDN web site shows how to customize how the error is presented to the user and how to customize the error message: http://msdn.microsoft.com/en-us/library/bb398934.aspx

 In server code you can customize error handling by setting the AsyncPostBackErrorMessage property and handling the AsyncPostBackError event of the ScriptManager control. In client code you can customize error handing by handling the endRequest event of the PageRequestManager class.

You can add the following javascript immediately after your ScriptManager declaration to suppress this error:

   <script type="text/javascript" language="javascript">
    Sys.WebForms.PageRequestManager.getInstance().add_endRequest(EndRequestHandler);
    function EndRequestHandler(sender, args) {
        if (args.get_error() != undefined) {
            var errorMessage;
            if (args.get_response().get_statusCode() == '200') {
                errorMessage = args.get_error().message;
            }
            else {              
                // Error occurred somewhere other than the server page.
                errorMessage = 'An unspecified error occurred. ';                                  
            }
            args.set_errorHandled(true);              
        }
    } </script>

See further details here: http://stackoverflow.com/questions/1271176/sys-webforms-pagerequestmanagerservererrorexception

Stop running this script? A script on this page is causing your browser to run slowly...

...If it continues to run, your computer might become unresponsive.

From a client perspective this may be prevented by doing the following:

·         Open Internet Explorer.

·         On the Tools menu, click Internet Options.

·         In the Internet Options dialog box, click Advanced.

·         Click to select the Disable script debugging check box.

·         Click to clear the Display a notification about every script error check box.

·         Click OK

For the intrepid techie, there is also a registry setting tweak you can attempt for overcoming this problem: See Miscorsoft support article here: http://support.microsoft.com/default.aspx?scid=kb;en-us;Q175500

From a developer perspective check out this blog entry: http://www.picnet.com.au/blogs/Guido/post/2010/03/04/How-to-prevent-Stop-running-this-script-message-in-browsers.aspx

A further option for developers is using the IE8 Developer Tools JScript Profiler. Look this up on the MSDN blog here:
http://blogs.msdn.com/b/ie/archive/2008/09/11/introducing-the-ie8-developer-tools-jscript-profiler.aspx

It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level

• Most likely cause is if you have nested web.config files. Remove or rename the one in a folder below or above your app's main folder.
• Also go into the IIS MMC and check that directory is configured as an application ...(http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/b5488995-fa99-460f-96d7-29d1ddcf3fac.mspx?mfr=true)

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.