Friday, April 19, 2013

Dolakha Kalinchowk Trek

Dolakha Kalinchowk Trek

Kalinchowk, residing at a height of above 3,700m is accessible from a drive from Kathmandu to Charikot and further 6-7 hours continuous trekking upward the hill. This is considered to be one of the non touristic trekking regions in eastern Nepal. The view of Ganesh Himal, Shisha Pangma, langtang, Dorje Lakpa, Jugal Himal, Gauri Shankar etc. are clearly visible in fine weather condition through this route. Tremendous beauty from the high hill of Kalinchowk takes your breath once giving means to visit of this region. Dolakha Kalinchowk trek is unique product for cultural study and exploring natural beauties. It has various wonder of biodiversities and culture. Varieties of culture, unexplored inner site of local lifestyle and religious sites, daily activities are the main attraction of this area. So far it is completely stand as non touristy area. To trek in this area will directly or indirectly contribute for the local as little income


Travel In Sindhuli Ghadi In Nepal

Sindhuli District(Nepali: सिन्धुली जिल्ला a part of Janakpur Zone, is one of the seventy-five districts of Nepal, a landlocked country of South Asia. The district, with Sindhulimadhi Kamalamai as its district headquarters and covers an area of 2,491 km². In 2001 it had a population of 279,821, in 2011 the population was 296,192.

Historical Importance

This place has a huge historic significance. The Sindhuli Gadhi in Sindhuli is the place where British soldiers were defeated for the first time in Asia in 1767 A.D . The British under the leadership of Captain Kinloch came to help the then ruler of Kathmandu, Jai Prakash Malla against the attack of Prithvi Naraya Shah. The Gurkha soldiers were familiar with the terrain and they utilized it to the fullest. The British Army had advanced weaponry such as guns and cannons whereas the Gurkha were with bows and arrows, spears, etc. But the Gurkhas fought bravely and eventually defeated the British. The British ran for their lives and retreated leaving behind the weapons they brought together with them. Some of these weapons can still be found in Sindhuli Gadhi.








Monday, January 21, 2013

How to fix Error 0x80070522: A required privilege is not held by the client in Windows 7

Error 0x80070522: A required privilege is not held by the client

Solution

1. Reboot into Safe Mode.

2. Log on as Administrator.

3. Click Start

4. Type the three letters cmd

5. Press Ctrl+Shift+Enter

6. Run the process as Administrator.

7. Type the following commands and press Enter after each:

    takeown /f d:\ /a /r /d y
    cacls d:\  /t /c /g administrators:F  System:F  everyone:F
    (Answer "yes" when prompted "Are you sure?")

The commands will make you the owner of drive D: and will give full access to everyone to all of its folders.

Wednesday, December 12, 2012

Thursday, June 14, 2012

Failed to access IIS metabase.

Problem
Failed to access IIS metabase.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Web.Hosting.HostingEnvironmentException: Failed to access IIS metabase.

The process account used to run ASP.NET must have read access to the IIS metabase (e.g. IIS://servername/W3SVC). For information on modifying metabase permissions, please see http://support.microsoft.com/?kbid=267904.
Solution :-
This Error Caused Because You Not Have Register ASP.Net with IIS.Please Follow Following Step to Regiser ASP.Net With IIS.
-> Go to Start - > Run -> Cmd.

-> GO to Your System Drive Mostly C Drive.

-> Type C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i
Just wait And Message comes Successfully Register.

Tuesday, April 17, 2012

SQL Server backup and restore to network drive

Problem Sometimes there is a need to backup or restore your database to another server because of a lack of available disk space on the current server. In this situation you have no other choice but to either remove unneeded files, find additional local storage or backup/restore across the network to another server. When using Enterprise Manager you can only see the local drives, so how do you address the drives on the other server? Solution Although SQL Server does not support browsing drives on other servers you do have the ability to use UNC (Universal Naming Convention) notation to address another server on your network. With a UNC path you can specify any server and any share in your network as long as you have access to read and write to these shares. So instead of using the GUI to browse through the available drives and selecting the directory where you want to write your backup file, you would specify the UNC path for the server such as the following: Do the following to create a backup: Click on Add... Instead of using the ellipses (...) to browse the drives, type in the UNC path along with the file name and select OK. At this point select OK to start the backup. In this example the backup file for the Northwind database will be placed on the "F$" share of server "server25". For each logical drive that exists on a server there is a corresponding $ share for each drive. So for example if you had a C, D and E drive you could access these shares as C$, D$ and/or E$. In order to access the administrator shares you need to have administrator access on the corresponding server or grant specific access to use these default shares. In addition, you can create shares on your server such as SQLBACKUPS which could correspond to a directory such as "F:\SQLServer\Backup". This would enable you to specify the backup for this folder as: \\server25\sqlbackup\northwind.bak To do a restore the same process should be followed: Click on Select Devices... Click on Add... Type in the UNC path along with the backup file name and click OK. Click OK and OK on the next screen to start the restore. As you can see there is not much too it, but having this ability makes life a lot easier especially in cases where you don't have enough disk space on the local server.