if you are using subversion as a organization data repository, then some times you are facing issue for commenting code on Subversion repository. below trick will helps you to resolve this issue.

This script needs to be keep under /{repository-location}/hooks/.
you will be find some templates script already there within the same folder structure.and for this you need to do slide modification.

Below is the script :

@echo off
:: Stops commits that have empty log messages.

@echo off


rem Subversion sends through the path to the repository and transaction id
set REPOS=%1
set TXN=%2

rem check for an empty log message
svnlook log %REPOS% -t %TXN% | findstr . > nul
if %errorlevel% gtr 0 (goto err) else exit 0

echo. 1>&2
echo Your commit has been blocked because you didn’t give any log message 1>&2
echo Please write a log message describing the purpose of your changes and 1>&2
echo then try committing again. — Thank you 1>&2
exit 1


This article will describe how we can remotely restart, shutdown, log off or even abort a system shutdown in our Local/Network machines using Remote Shutdown Tool (shutdown.exe).

We can use the Remote Shutdown Tool with GUI or from the command prompt but we need to have administrative privileges on those machines.

We can start the GUI of Remote Shutdown Tool by executing:—

shutdown.exe /i

If we need to use the command line tool here are the options:

Note: We can use the – switch in case / switch does not work or vice versa

Usage examples:
Restart a network machine and force any running applications to close

shutdown /m \\computername /r /f

Abort a previous shutdown command

shutdown /m \\computername /a

Shutdown a network machine and force any running applications to close

shutdown /m \\computername /s /f

Logoff a machine and force any running applications to close (This cannot be used with /m to specify the target machine)

shutdown computername /l /f

Hibernate a local machine and force any running applications to close

shutdown /m \\computername /h /f

Note: By default the time-out period in previous examples is set to 30 seconds.

Restart a network machine and force any running applications to close giving a reason and set the time-out period to 1 minute (120 sec)

shutdown /m \\computername /r /f /c “Computers will restart in 1 minute, please save any work. System Administrator” /t: 120

Schedule a restart of a machine:

at 23:00 /every:M,T,W,Th,F shutdown /r /m \\computername

In case we want to shutdown/restart multiple network machines through a batch file have a look at the following :—

This article will describe how to shutdown remote network computers by using a small batch script to loop into each hostname/ip line within a text file and issuing the shutdown command to the computer(s).

The above code will take an argument for the shutdown time which we specify while running the script:

@echo off
if “%1″==”” goto fin
for /f “tokens=1″ %%i in (computers.txt) do ^
shutdown -s -t %1 -f -m \\%%i

Explaining the above code we first check if an argument exist so it continues with the batch file else it ends.
For each hostname/ip inside the computers.txt it executes the shutdown command for each remote machine inside the network.

We could even simplify the script without asking for any arguments with the following snippet:

@echo off
for /f “tokens=1″ %%i in (computers.txt) do ^
shutdown -s -t 30 -f -m \\%%i

The -t 30 is for the time limit which by default is 30 if you do not specify that option.
The -s option shutdown the computer.
The -f option forces the application to close while the system shutdown without asking the user to interact.
The -m option is to specify the computer(s) hostname/ip.

After we finish with the batch file we can schedule it to run through a domain admin account to remotely shutdown the network computer(s) at specific times and dates.


In this article we will briefly explain rdesktop client and how we can connect to Windows Terminal Services for Remote Desktop Protocol (RDP). The rdesktop client supports all version of Microsoft Windows including the latest Windows Server 2008 Operating System and it runs on most unix based platforms as well as other ports.

How to Download and Install:—-

1) wget http://garr.dl.sourceforge.net/sourceforge/rdesktop/rdesktop-1.6.0.tar.gz
2) tar -zxf rdesktop-1.6.0.tar.gz
3) cd rdesktop-1.6.0
4) ./configure
5) make
6) make install


rdesktop -k en-us -a 16 -f -u username -p “password” server

Command Options Used:
-f switch for full screen mode
-k for keyboard layout on server
-a for color depth
-u for username
-p for password

Note: To exit full screen mode press: CTRL + ALT + Enter

Full Usage Options:-

Usage: rdesktop [options] server[:port]
-u: user name
-d: domain
-s: shell
-c: working directory
-p: password (- to prompt)
-n: client hostname
-k: keyboard layout on server (en-us, de, sv, etc.)
-g: desktop geometry (WxH)
-f: full-screen mode
-b: force bitmap updates
-L: local codepage
-A: enable SeamlessRDP mode
-B: use BackingStore of X-server (if available)
-e: disable encryption (French TS)
-E: disable encryption from client to server
-m: do not send motion events
-C: use private colour map
-D: hide window manager decorations
-K: keep window manager key bindings
-S: caption button size (single application mode)
-T: window title
-N: enable numlock syncronization
-X: embed into another window with a given id.
-a: connection colour depth
-z: enable rdp compression
-x: RDP5 experience (m[odem 28.8], b[roadband], l[an] or hex nr.)
-P: use persistent bitmap caching
-0: attach to console
-4: use RDP version 4
-5: use RDP version 5 (default)

There is also a graphical user interface (GUI) that you can use named Terminal Server Client [tsclient]

Ref URL :- http://sourceforge.net/projects/tsclient


You are getting this error in the Application log of the computer that is running Sharepoint Services 3: “The database WSS_Content on ComputerName\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures”

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Topology
Event ID: 6800 Date: 10/17/2008
Time: 8:09:40 PM
User: N/A
Computer: ComputerName
Description: The database WSS_Content on ComputerName\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

This is because SPWebService instance failed to finish provisioning and the status of that service is marked as provisioning.


1. Start -> Run type cmd and OK
2. cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>
3. Start & Stop the SPWebService

* stsadm -o provisionservice -action stop -servicetype spwebservice -servicename “”

* stsadm -o provisionservice -action start -servicetype spwebservice -servicename “”

4. After the SPWebService started

* stsadm -o upgrade -forceupgrade -inplace
* psconfig -cmd upgrade -inplace b2b -wait -force

There are also cases reporting that the issue can occur prior to installation of GroupBoard KB installation



This article will explain how to use Microsoft Office 2007 Inbox Repair Tool (scanpst.exe) which is included with Microsoft Office 2007 to recover your PST Personal Folders which include Mail, Calendar, Contacts, Tasks, Notes, Folder List, etc. From time to time your Outlook .pst file might get corrupted or damaged and for that we can use scanpst.exe to validate and correct errors in .pst files.

Note: The above tool can also fix corrupted/damaged .OST files

By default the scanpst.exe tool is installed with Microsoft Office 2007 Installation

For 32bit users the scanpst tool is located under:
%ProgramFiles%\Microsoft Office\Office12

For 64bit users the 32-bit scanpst tool is located under
%ProgramFiles(x86)%\Microsoft Office\Office12

How can we do this?????

1. Start -> Run -> %ProgramFiles%\Microsoft Office\Office12\SCANPST.EXE

2. Click on Browse… and select the corrupted/damaged .pst file and click on Start

3. Wait until the Inbox Repair Tool scans your .pst file

4. If your .pst file can be recovered when the scan finish you will have to click on Repair button to start the recovery

For more information you can check the following Microsoft Article located at