Failed to retrieve data for this request ms sql ошибка

  • Remove From My Forums

  • Question

  • I have an issue while trying to install SQL Server 2014, the error that I received is failed to retrieve data for this request. 

    The end of the file Details.txt is the followingL

    (09) 2018-07-26 14:10:08 Slp:    — End of inner exception stack trace —
    (09) 2018-07-26 14:10:08 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (09) 2018-07-26 14:10:08 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
    (09) 2018-07-26 14:10:08 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
    (09) 2018-07-26 14:10:08 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
    (01) 2018-07-26 14:10:08 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    (01) 2018-07-26 14:10:08 Slp: Inner exceptions are being indented
    (01) 2018-07-26 14:10:08 Slp: 
    (01) 2018-07-26 14:10:08 Slp: Exception type: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
    (09) 2018-07-26 14:10:08 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
    (01) 2018-07-26 14:10:08 Slp:     Message: 
    (01) 2018-07-26 14:10:08 Slp:         Failed to retrieve data for this request.
    (01) 2018-07-26 14:10:08 Slp:     HResult : 0x80131500
    (01) 2018-07-26 14:10:08 Slp:     Data: 
    (01) 2018-07-26 14:10:08 Slp:       HelpLink.ProdName = Microsoft SQL Server
    (01) 2018-07-26 14:10:08 Slp:       HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
    (01) 2018-07-26 14:10:08 Slp:       HelpLink.LinkId = 20476
    (01) 2018-07-26 14:10:08 Slp:     Stack: 
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.ProcessDTbl(DataTable dt, Int32 level)
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectSqlDiscoveryData(String machineName)
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.CollectDiscoveryData(String machineName)
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
    (01) 2018-07-26 14:10:08 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    (01) 2018-07-26 14:10:08 Slp:     Inner exception type: System.ComponentModel.Win32Exception
    (01) 2018-07-26 14:10:08 Slp:         Message: 
    (01) 2018-07-26 14:10:08 Slp:                 Not all privileges or groups referenced are assigned to the caller.
    (01) 2018-07-26 14:10:08 Slp:                 
    (01) 2018-07-26 14:10:08 Slp:         HResult : 0x80004005
    (01) 2018-07-26 14:10:08 Slp:         Error : 1300
    (01) 2018-07-26 14:10:08 Slp:         Stack: 
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege.SetPrivilege(Boolean enable)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Configuration.Sco.AdjustTokenPrivilege..ctor(String privilege)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Configuration.Sco.SqlRegistry.GetLocallyCachedLocalMachineSubKey(ServiceContainer ctx, String machineName, SqlRegistryKey key)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Discovery.DiscoveryUtils.TryLocallyCacheRegistryKey(ServiceContainer ctx, String machineName, SqlRegistryKey machineKey, String registryPath, RegistryView
    regView, String regPath, RegistryAccess registryAccess, Boolean& alreadyCached)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Discovery.DiscoveryUtils.GetLocalMachineSubKey(ServiceContainer ctx, String machineName, RegistryView regView, String regPath, RegistryAccess registryAccess)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.GetSql2kMsiInstanceListInHive(String machineName, RegistryView regView)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Discovery.DiscoveryEnumObject.LoadSql2kInstanceList(String machineName)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Discovery.Product.GetData(EnumResult erParent)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData()
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Management.Sdk.Sfc.Environment.GetData(Request req, Object ci)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.GetData(Object connectionInfo, Request request)
    (01) 2018-07-26 14:10:08 Slp:                 at Microsoft.SqlServer.Management.Sdk.Sfc.Enumerator.Process(Object connectionInfo, Request request)

Источник
  • Remove From My Forums

  • Вопрос

  • I am getting this error, every time I expand a node in object explorer. I can’t view any of my databases I got two there the error is:

    TITLE: Microsoft SQL Server Management Studio
    ——————————

    Failed to retrieve data for this request. (Microsoft.SqlServer.Management.Sdk.Sfc)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

    ——————————
    ADDITIONAL INFORMATION:

    An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

    ——————————

    Database ‘msdb’ cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. (Microsoft SQL Server, Error: 926)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1617&EvtSrc=MSSQLServer&EvtID=926&LinkId=20476

    ——————————
    BUTTONS:

    OK
    ——————————

    I checked Microsoft article about this and I am still getting the error: 

    I’m a PC and I run Left For Dead 2 :)

    • Изменено

      9 февраля 2013 г. 15:11

Ответы

  • Hello,

    The error is actually possible corruption with the MSDB system database:

    Database ‘msdb’ cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.

    Please run DBCC CHECKDB(‘MSDB’) WITH ALL_ERRORMSGS, NO_IFNOMSGS and let us know what the output is.

    -Sean

    Sean Gallardy | Blog |
    Twitter

    • Предложено в качестве ответа
      Naomi N
      10 февраля 2013 г. 4:56
    • Помечено в качестве ответа
      Maggie Luo
      20 февраля 2013 г. 17:26

  • Hello all,

    From the error:

    Database ‘msdb’ cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. (Microsoft SQL Server, Error: 926)

    Its evident that msdb is corrupt.

    Supported way to recover the database would be to restore the last known good backup:

    http://msdn.microsoft.com/en-us/library/ms190749(v=sql.105).aspx

    • Помечено в качестве ответа
      Maggie Luo
      20 февраля 2013 г. 17:26

Источник

Today I faced a strange issue when I tried to install a new SQL Server instance : Failed to retrieve data for this request
This error occurred just after clicking on “New SQL Server stand-alone installation…”

The error message is not helpful at all. So, the first step to troubleshoot an issue is to look at the error logs.

The location by default is : C:Program FilesMicrosoft SQL Server140Setup BootstrapLog
There is a summary.txt file and many subfolders created every time the Installation wizard is started. In those subfolders, we can find a Detail.txt file.

The error looks like this:

Exception type: Microsoft.SqlServer.Management.Sdk.Sfc.EnumeratorException
    Message: 
        Failed to retrieve data for this request.
    HResult : 0x80131500
    Data: 
      HelpLink.ProdName = Microsoft SQL Server
      HelpLink.BaseHelpUrl = http://go.microsoft.com/fwlink
      HelpLink.LinkId = 20476
      HelpLink.EvtType = [email protected]@[email protected]
      DisableWatson = true
    Stack: 
        at Microsoft.SqlServer.Discovery.SqlDiscoveryDatastoreInterface.LoadData(IEnumerable`1 machineNames, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
        at Microsoft.SqlServer.Discovery.SqlDiscoveryProvider.DiscoverMachines(ServiceContainer context, Boolean runRemoteDetection, String discoveryDocRootPath, String clusterDiscoveryDocRootPath)
        at Microsoft.SqlServer.Configuration.SetupExtension.RunDiscoveryAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)
    Inner exception type: Microsoft.SqlServer.Configuration.Sco.SqlRegistryException
        Message: 
                The network path was not found.
                
        HResult : 0x84d10035
                FacilityCode : 1233 (4d1)
                ErrorCode : 53 (0035)

The useful information here is the message about network: The network path was not found.
I try to install the instance on a server that is a member of a Failover Cluster. So this gives me a hint.
I need to check any connectivity issue between the 2 nodes of my cluster.

The 2 nodes can ping each other. The DNS resolution is fine.
Out of curiously, I tried the administrative shares and it was not working from my current server to the other node. The other way around is fine. This is surprising and I tried to fix this.

Without further ado, I will show you where the issue comes from.

Someone had disabled File and Printer Sharing for Microsoft Networks on the Ethernet Adapter of the other cluster node.

Enabling it made both the administrative shares and the SQL Server Wizard behave as expected.

I hope this was helpful if you encountered the same error message when trying to install an SQL Server instance in a Failover Cluster context.

Post Views: 3,407

We use cookies on our website to provide you with the most relevant experience by remembering your preferences. No personal data is stored. By clicking on «Accept All», you consent to the use of ALL cookies. However, you can visit «Cookie Settings» to provide controlled consent. Read More

Источник

I have been writing a program in c# using Visual Studio 2012. This program makes numerous calls to the database, and everything has always worked perfectly; never had to mess with any configurations to get it to run. A few days back, I received a new computer. After setting everything up, I was trying to run my program but it kept failing on the database calls because it was timing out. I deleted the old connection string and tried connecting to our backup database. Using the Server Explorer, I created a new connection; after filling in all the information, I used the Test Connection button and was told the test succeeded. From the server explorer, I then tried opening the Tables folder, but it didn’t work. After about 30 seconds, I got the following error:
Failed to retrieve data for this request.
Lock request time out period exceeded.

I tried refreshing the connection several times, restarting the db, restarting visual studio, even restarted my computer. I tried connecting back to the original db and got the same result, so I’m sure it’s computer-specific and not related to the db. I have already verified that the windows account I am logged on as is a sysadmin. We use SQL Server Authentication, and the account Visual Studio is attempting to connect to is also a sysadmin. I have completely disabled my firewalls as well. I have searched high and low on the internet for an answer, but the only cases where I could find error messages similar to mine were very specifically related to ASP. What I don’t understand (and what’s difficult to search for) is being able to successfully connect to the db, yet unable to retrieve any data. Any help would be greatly appreciated!

Additional Information:
I am using LINQ to SQL class in my project. Target framework = 4.5

Update:
I marked the answer as Accepted, but I’ll elaborate here in case anybody else ever runs into this same problem. There were two open processes, one of which belonged to me, which is what I assume was allowing the Test Connection to work. After killing all open processes, I wasn’t able to connect back to the DB at all. I then restarted the DB service (which is on our LAN, not local) and that worked. I no longer think it had anything to do with the new computer; it just happened simultaneously to whatever caused the issue and caused me to go down the rabbit hole.

Источник

  • Jon.Morisi

    SSChampion

    Points: 12846

  • richieStick

    Old Hand

    Points: 361

    Hi

    We have a secure network with vlans and multiple firewalls as well as the windows firewall on the servers. All I’m trying to do is connect to the integration server using the management studio from my PC — I can connect if I’m on the server using the same credentials.

    I suspect that the firewalls are the issue and DCOM being the problem.

    I’m investigating this and will come back with the results.

    Rich

  • Brandie Tarvin

    SSC Guru

    Points: 172957

    Another thought. Have you verified that the server accepts remote connections?

    That’s my suspicion if the only time it works is when you are on the server itself. On your desktop, log into SSMS (not SSIS) and try to connect to the server. See if it gives you a «server may not be set up for remote connections» kind of error or if you can log in.

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • richieStick

    Old Hand

    Points: 361

    Hi Brandie

    Yes, I can connect to the server if I want to connect to the database server using SSMS with no issues using the same admin credentials.

    Thanks anyway

    Rich

  • Brandie Tarvin

    SSC Guru

    Points: 172957

    Last question then. Are you using Bulk Insert tasks that are failing or is it the whole package with other tasks that are failing on connection?

    Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

  • richieStick

    Old Hand

    Points: 361

    Hi Brandie

    When you are using MS SQL Server Management Studio, one of the options is to connect to the Integration Server. It is this that I was having problems with. When I chose the Database Server it was fine. Nothing to do with any Packages or Visual Studio.

    The problem turned out to be firewalls and DCOM (we have strict security).

    Thanks anyway.

    Rich

  • richieStick

    Old Hand

    Points: 361

    It was the firewalls and DCOM. Security is such that we can’t do much without a rule in the firewall. Trouble is that DCOM isn’t firewall friendly and SSMS uses DCOM to talk to the Integration Server. Adding port 135 and the Integration Service Program wan’t enough. Had to allow all ports to be able to connect from specific PCs.

    Rich

Viewing 8 posts — 1 through 7 (of 7 total)

Источник

  • Failed to open descriptor file как исправить ошибку
  • Failed to map file ошибка
  • Failed to locate driver file как исправить ошибку
  • Failed to load installation components как исправить ошибку
  • Failed to load il2cpp rust ошибка