:::: MENU ::::

Posts Categorized / Windows Server

  • Sep 23 / 2013
  • 0
dbDigger, Linked Servers and remote data, System Administration, Windows Server

Copy paste not working during remote desktop sessions

I use Remote Desktop utility to get connect to the online servers if required. While using the remote desktop it enables us to share the clipboard among both the OS to copy the data. A couple of days back i noticed that i am no more able to copy data from or to my laptop from the server connected through remote desktop. It was problematic and first thing that came to mind was that i should verify the local resources settings in my remote desktop connection panel. It had following settings and nothing was wrong here

Data copy not working on remote desktop session

So now i had to google for any further clue and I found the reason in a minute by googling. I performed following steps to solve the issue.

  • Login to the remote server on Remote Desktop
  • Open task manager (by right clicking on taskbar)
  • Go to Processes tab
  • Search the process RDPClip.exe
  • End the process RDPClip.exe
  • Go to Applications tab in task manager
  • Click on New Task and start RDPClick.exe by entering in box

The issue is solved here. We may also implement the same  solution through following cmd commands for the same tasks
Taskkill.exe /im rdpclip.exe
Rdpclip.exe

  • Oct 25 / 2012
  • 0
DBA Interview questions, dbDigger, Monitoring and Analysis, Ports, System Administration, Windows Server

How to identify the active port/ports of SQL Server DB engine

In previous post i have discussed the ports configuration for SQL Server database engine. For any SQL Server instance what are the options to identify the active ports? For this purpose we have three major methods to identify the SQL Server port through GUI. We may use undocumented extended stored procedure master..xp_regread system  to read the registry value for this purpose.However in this post i would cover only the major GUI methods to discover the active TCP/IP port for any SQL Server instance.

  • Through SQL Server Logs
  • Through SQL Server Configuration Manager
  • Through Windows Application Event Viewer

 Through SQL Server Logs

We may use xp_readerrorlog SP in SSMS or SSMS GUI to determine the current port for SQL Server. Execute the SP in SSMS query pane and get the results

 USE master   
 GO   
 xp_readerrorlog 0, 1, N'listening on', 'any', NULL, NULL, N'asc'   
 GO   

Same may be determined through SSMS GUI

identify the active port of SQL Server through SSMS GUI

Through SQL Server Configuration Manager

Go to SQL server configuration manager and open TCP/IP properties in network configurations of specific instance. It would show the active TCP/IP port for SQL Server. Port may be noted or even changed to a specific static one here.

Identify SQL Server port through Configuration Manager

Through Windows Application Event Viewer

Another major option available for port discovery is through Windows event viewer. Find the event viewer in Windows Administrative Tools and go to application logs folder. There you may get the port information for your specific SQL Server instance.

Identify SQL Server port through Windows event log viewer

This is not the end, there would be some other ways to discover the same information. Also read the post and comments section on MSSQLTips for same issue.

  • Feb 24 / 2012
  • 0
Backup and Restore, dbDigger, SQL Server Error messages, SQL Server IO, System Administration, Windows Server

Database backup and restore failed on mapped network drive

During my job at National Database and Registration Authority of Pakistan (NADRA), i was accustomed to create database backups directly on mapped network drives. We have a domain configured at NSRCs with SQL Server 2000. Fore servers with single disk, it becomes very efficient by preventing the local server disk IO. Now while working with SQL Server 2005 installed on windows server 2003 work group. i was required to create an adhoc backup during peak hours. For optimized IO i tried to use mapped network drive for creating backup on it directly. But surprisingly mapped network drive was neither available in SSMS backup location explorer nor through T-SQL backup statement. Error message was being generated.

Database backup and restore on mapped network drive

Same statement was working successfully for any location other than mapped network drive. Keeping in view my previous experience with SQL Server 2000 on domain i was not expecting any problem in this task. However after some time i realized that network drive is not available as backup device.

Next option was BOL and Google. There i came to know that mapped network drives are available for backups only when your SQL Server service is running under domain account that has access to mapped network drive.

Conclusion

Without a privileged domain account as start up account of SQL Server service, mapped network drives cannot be accessed from within SQL Server context for backup or restore process.

  • Feb 22 / 2012
  • 0
dbDigger, Deployment, SQL Server Error messages, System Administration, Windows Server

Role management tool to install or configure .Net framework on Windows Server 2008

While installing SQL Server 2008 on Windows Server 2008 R2, i got following error message at initial stage in process.

Error message in SQL Server 2008 setup related to Role management tool

Windows was up to date and required version of .Net framework was installed on it. Opened Server Manager for Windows Server 2008 and clicked on features in left panel. Then by clicking Add Features link in right panel another panel was opened with several features available there for installation. I checked the box for my required .Net framework feature and Clicked on Next button to proceed with the installation.

Service Manager in Windows Server 2008 for .Net Framework features

The .Net feature was installed and SQL Server 2008 installation ended successfully.

  • Feb 21 / 2012
  • 0
dbDigger, SQL Server Services, System Administration, Windows Server

Not able to connect SQL Server 2008 on network

Recently i deployed SQL Server 2008 along with SP3 on Windows Server 2008 R2. All installation and later configuration were managed through Remote Desktop. Later while trying to connect the instance on LAN from my desktop PC i got following error message

Not able to connect SQL Server 2008 on network

The generated error message is related to network access of instance. Back through remote desktop, first of all i checked for firewall issues but every thing was fine for that. Then after little exploration of SQL Server configuration manager i observed that TCP is disabled. I enabled the TCP in configuration manager as shown in snap

Enable TCP IP in SQL Server configuration Manager

A warning box appeared suggesting the SQL Server service restart for changes to take effect.

SQL Server Service restart required after enabing TCP IP

I restarted the service from configuration manager and again tried login from desktop PC on LAN. This time login was successful without any error message.
So make sure to enable TCP-IP for accessing the SQL Server 2008 instance on LAN. TCP-IP is by default disabled in SQL Server 2008 installation.

  • Dec 14 / 2011
  • 0
DBA Interview questions, dbDigger, Deployment, SQL Server Training, SQL Server versions and editions, Windows Server

SQL Server editions and Windows platform

Each of SQL Server release like SQL Server 2000, SQL Server 2005 and SQL Server 2008 is further categorized in editions based on their features and capabilities. For example, edition of a specific release may be any of following

  • Data center edition
  • Enterprise edition
  • Standard edition
  • Developer edition
  • Express edition
  • Apart from these there may be some other editions like run time edition or web edition. Some editions like Data center edition or enterprise edition can only be installed on Server OS while others may be installed on both server or client OS.
    For windows platform the term Server OS refers to different editions of

  • Windows server 2000
  • Windows server 2003
  • Windows server 2008
  • Windows server 2008 R2
  • While for windows platform, client OS would be any edition of following

  • Windows 2000
  • Windows XP
  • Windows vista
  • Windows 7
  • So while installing any SQL Server version, do consult the requirements related to OS.

    Pages:12
    Consult us to explore the Databases. Contact us