Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

I am using SQL Server Management Studio with the following version information below:

Microsoft SQL Server Management Studio              10.50.4000.0
Microsoft Data Access Components (MDAC)             3.85.1132
Microsoft MSXML                                     2.6 3.0 4.0 5.0 6.0 
Microsoft Internet Explorer                         6.0.2900.5512
Microsoft .NET Framework                            2.0.50727.3053
Operating System                                    5.1.2600

When i try to use Task->Import Data.. i get error like shown below

enter image description here

The SQL server engine is 2008 R2 and the user is sysadmin. Also this error is occuring on all instances of SQL (both local and network) instances. I tried giving full permissions for the user on the SQL server installation folder. But that didn't help. So what might be the reason for this error? If you want any more information please write me.


I checked the process monitor for process DTSWizard.exe(used for import in sql) has about 160,000 events. Then i searched for "denied" in those. I got a registry entry showing "ACCESS DENIED" .Same is shown below.

enter image description here

Now i searched for that particular registry. But that registry entry was not there in the PC having problem.

Then i searched same registry entry in some other PC where there is no error for SQL import data. but in other PC also i didnt get same registry. But in these PC there where no ACCESS DENIED error in process monitor.

Now by using the process monitor events and access denied registry how can i trace the problem?

share|improve this question
Could you try running process monitor technet.microsoft.com/en-us/sysinternals/bb896645.aspx to find out what access is being denied and report back? –  Edward Dortland Jan 9 '14 at 9:01
I have seen most of this kind of errors are advised to solve by using process monitor. But in process monitor process DTSWizard.exe(used for import in sql) has about 160,000 events.How to track the error in that huge number of events? –  IT researcher Jan 9 '14 at 9:10
At least we've now narrowed it down only 160k events. ;-) On a more serious note, try filtering on the result column. Exclude things like Success, buffer overflow. etc that would narrow it down to "only" 1k or 2k. –  Edward Dortland Jan 9 '14 at 9:27
Just to confirm with you since the answers being given assume differently. You are receiving this error before you are even dialing in a SQL server name correct? I'm assuming this since your data source windows is still empty. –  Edward Dortland Jan 9 '14 at 12:56
@EdwardDortland I have updated my question with process monitor results.Please check. Also what u mean by "your data source windows is still empty" in your previous comment? I am getting error while i click on import data in ssms.(before entering the data source-same can be seen in image also) –  IT researcher Jan 10 '14 at 8:05

2 Answers 2

Did you install Sql Server on a seperate windows account or on the one you are using ? Is the database yours? If you restored a db from a bak and it was created on a different machine or instance or perhaps under a different account, try changing the owner of the db. Also, what's with the protocols? Did you made any changes in the MSSQL Configuration Manager? Try set the "VIA" property to Disabled

Did you install the latest update for MSSQL Server?

share|improve this answer
Yes its installed from same user and database are from same server –  IT researcher Jan 21 '14 at 8:10

Rght click on SSMS, Run as administrator, sometimes this error appears. Once i couln't attach mdf file to database due this error.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.