Now to see if it will complete successfully.

Related posts

• No related posts.

Today, I came across a Windows Service on a server that I inherited. By the name of the service I could tell that it was built in-house and I even found enough information to determine who the developed it.  However, since it was not in the Add / Remove Programs list of the Control Panel, I wasn’t sure how to remove it.  So, I found the following on Geeks With Blogs – Shahed’s Blog:

Recently, I was trying to delete a windows service. Normally it should not be necessary to manually delete a service. Uninstalling an application should remove its associated service (if any).

However, I installed some beta products and a service created by one of the applications was not removed automatically. Its very easy to remove a service from registry if you know the right path. Here is how I did that:

1. Run Regedit or Regedt32

2. Find the registry entry "HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services"

3. Look for the service there and delete it. You can look at the keys to know what files the service was using and delete them as well (if necessary).

alternatively, you can also use command prompt and delete a service using following command:

sc delete < SERVICE name>
or to create, simply type
sc create <SERVICE name>

Update:
If you have space in the file path you need to use quotation marks ("). For example: 
sc create "MySQL" binpath= "C:\Archivos de programa\MySQL\MySQL Server 5.1\bin\mysqld.exe"

I used the “sc delete” method to remove the service.

Thanks, Shahed!

Related posts

• No related posts.

Below is the command that you use from the command line:

Description: list IIS application pools and associated worker process
             Recycle application pools.

Syntax: IIsApp.vbs [{ /a  | /p
 } [/r] ]

Parameters:

Value              Description
/a    Specify an application pool by name. Surround
                    with quotes if it contains spaces.
                   If used alone without an accompanying action,
                   IIsApp.vbs will report PIDs of currently running
                   w3wp.exe processes serving pool .
/p
           Specify a process by process ID. If used alone
                   without an accompanying action, IIsApp.vbs will
                   report the AppPoolId of the w3wp process specified
                   by
. When a PID is specified with /r, that PI
                   is mapped to an application pool and the action is
                   taken upon the application pool. If a PID is given
                   for a web garden, i.e. an application pool served
                   by more than one w3wp, then all w3wp's for that
                   application pool will be acted upon.
/r                 Recycles the application pool.

DEFAULT: no switches will print out the PID and AppPoolId.

Examples:

IIsApp
IIsApp /p 2368
IIsApp /a DefaultAppPool /r
IIsApp /p 2368 /r

Related posts

• No related posts.

SMTP relay behavior in Windows 2000, Windows XP, and Exchange Server

The basic test:

Start a command prompt.

Type telnet ServerName 25, where ServerName is the SMTP server name or IP address and 25 is the port number, and then press ENTER.

Type EHLO, and then press [ENTER].

At the Telnet session prompt, type RSET. The telnet session responds with text that is similar to the following:

1. 250 2.0.0 Resetting

2. Type MAIL FROM:UserName@DomainName.tld, where UserName is the name of the user, DomainName is the name of the domain, and tld is the top level domain such as .com or .net.
   The telnet session responds with text that is similar to the following:

3. 250 2.1.0 UserName@DomainName.tld….Sender OK

4. Type RCPT TO:RecipientName@DomainName.tld, where RecipientName is the e-mail address of the recipient.
   The telnet session responds with text that is similar to the following:

5. 550 5.7.1 Unable to relay for RecipientName@ DomainName.tld

Related posts

• WssRemoveFeatureFromSite + BAT File (0)
• WSS v3 & MOSS 2007 Features (0)
• Unable To Enable Office SharePoint Server Publishing (0)
• Unable To Activate Office SharePoint Server Publishing Infrastructure (0)
• Stop Windows SharePoint Services Web Application (0)