Tuesday, April 26, 2011

Grant User Rights to Start/Stop Windows Services

If you are an Administrator of Windows 2000/2003/xp operating system & need to grant rights for a user to Start/Stop an Windows Service, please follow the below steps.

1. Download & install Subinacl tool from microsoft

2. In Command Prompt,
SUBINACL /SERVICE [\\MachineName\]ServiceName /GRANT=[DomainName\]UserName[=Access]

where [\\MachineName\], [DomainName\] & [=Access] are optional

Example:
E:\Program Files\Windows Resource Kits\Tools>subinacl /service outlookmessengerLS /grant=xyzuser

outlookmessengerLS : new ace for xyzuser
outlookmessengerLS: 1 change(s)


Elapsed Time: 00 00:00:00
Done: 1, Modified 1, Failed 0, Syntax errors 0
Last Done : outlookmessengerLS

For more details:

Thursday, March 24, 2011

Stop Blue Screen 0x0000007E memory dump error

If you are experiencing Stop Error 0x0000007e (0xc0000005, 0x89c3e6e4, 0xb90d9a40, 0xb90d973c) regularly & exhausted on finding a solution try this :

Solution 1:
Try removing external cards(Sound Card, Network Card etc) of your mother board & check whether the issue is solved.
You can also try by uninstalling each Card driver.

Solution 2:
Any other conflicting/malfunctioning driver may also leads to this issue.
1. In Run, type sigverif & click Ok.
2. In Sigverif tool window, click Advanced, click Look for other files that are digitally not signed, click browse & select Windows\System32\Drivers folder, click Ok.
3. Run Start.
4. In the list of unsigned drivers, trace which are unknown & non essential drivers. Move the sys file to a backup folder. (Be careful, while moving the driver. Move only unsigned driver file)
5. Restart the system & make sure all are working normal without these drivers.

Solution 3:
Make sure you have sufficient hard disk space.

Done.



I Hope & Wish you will not get that Stop error again.

Long Live Windows!

Friday, January 7, 2011

MSSQL & Event ID: 17137

In Event Viewer > Application, If you have noticed Thousands of Events with details "Starting up database.." Event ID: 17137, here is the solution :

Make sure to set all the database in your SQL Server as Auto_Close=False. By default in SQL Server Express Editions, Auto_Close was set to True. If Auto_Close is true, SQL Server close the DB when the last connection is closed. So the databases were stopped & started regularly.

To Set Auto_Close = False
In SQL Server Manager > Right Click Database > Properties > Options, you can find the option.
OR
ALTER DATABASE SET AUTO_CLOSE OFF