Ошибка failed to retrieve data

NHL may sometimes fail to retrieve data in HUT. When this issue occurs, the following error message pops up on the screen: Failed to retrieve data, please try again later. Let’s see how you can get rid of this annoying error and resume playing NHL.

Check your connection

Make sure your connection is stable. Disconnect all the other devices using the connection to free up more bandwidth for NHL.

Additionally, unplug your router and leave it unplugged for one minute. Meanwhile restart your computer or console. Then plug your router back into the wall outlet, wait until your computer or console goes back online. Launch NHL again and check the results.

If possible, use a different connection. If you’re on Wi-Fi, switch to a cable connection. Try connecting to a mobile hotspot and check if NHL can retrieve data now.

Restart NHL

Try restarting the game a few times. Additionally, make sure to close all the unnecessary processes running in the background. They might be interfering with the game preventing it from retrieving data.

⇒ Learn more: How to get NHL Loyalty Rewards

Check your date and time settings

When your device connects to NHL’s servers, EA also checks you data and time settings for security reasons. If your date and time settings are incorrect, EA will automatically block your connection request.

Go to your computer or console settings, and let your device set up your date and time settings automatically.

Reinstall the game

If the issue persists, uninstall NHL and restart your device. Then reinstall NHL and check if the error persists. If your NHL game files got corrupted, installing a fresh copy of the game should fix the problem.

Contact EA Support

If NHL still fails to retrieve data, contact EA Support for further help. EA’s support agents will provide you with additional solutions to fix the problem.

Conclusion

To fix NHL error “Failed to retrieve data”, restart your router and switch to a cable connection. Then let your device set up your date and time settings automatically. If the error persists, reinstall NHL and contact EA Support.

First published on MSDN on Nov 12, 2009

1.



After connecting to SQL Server Integration Services 2005 from SQL Server Management Studio, when you expand MSDB under Stored Packages to see list of stored packages, you may get below error.

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

F


or help, click:

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

——————————

ADDITIONAL INFORMATION:

The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic «Configuring the Integration Services Service» in Server 2005 Books Online.

Login timeout expired

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].  (MsDtsSrvr)

——————————

Login timeout expired


An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.

SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].  (Microsoft SQL Native Client)

Cause and Resolution

SSIS uses the configuration file located on the machine at «%ProgramFiles%Microsoft SQL Server90DTSBinnMsDtsSrvr.ini.xml».  The content of file MsDtsSrvr.ini.xml typically looks like below.

<?xml version=»1.0″ encoding=»utf-8″?>

<DtsServiceConfiguration xmlns:xsd=»http://www.w3.org/2001/XMLSchema» xmlns:xsi=»http://www.w3.org/2001/XMLSchema-instance»>

<StopExecutingPackagesOnShutdown>true</StopExecutingPackagesOnShutdown>

<TopLevelFolders>

<Folder xsi:type=»SqlServerFolder»>

<Name>MSDB</Name>

<ServerName>.</ServerName>

</Folder>

<Folder xsi:type=»FileSystemFolder»>

<Name>File System</Name>

<StorePath>..Packages</StorePath>

</Folder>

</TopLevelFolders>

</DtsServiceConfiguration>

If the ServerName specified between ServerName tags above is incorrect, you get the similar error mentioned above.  To correct the issue, specify the correct name of the SQL Server with the instance name.

SSIS is not recommended to configure as a clustered resource, rather it is advised to install it separately on each node. Note, after installing in each node, by default SSIS will put “.” In the ServerName tag in the config file because SSIS is instance independent and always assumes to be installed on the default instance (which is “.”). So, in a clustered environment we need to specify “ClusterVirtualNameInstance name” where MSDB Database is hosted.

We need to restart the SSIS Windows Service for the changes to take effect.

2


When you try to connect to SQL Server Integration Services 2005 from SQL Server Management Studio from a client computer and the you use a user account that is not a member of the Administrators group on the sever, you may get below error.

Cannot connect to <computer-name>.

——————————

ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

——————————

Connect to SSIS Service on machine <computer-name> failed:

Access is denied.

If you use the same user account to connect to SQL Server Integration Services 2005 from SQL Server Management Studio locally on the server, you will be able to successfully connect.

Cause and Resolution

This is a permission related issue. Please follow workaround provided below KB article to resolve the error.

940232

— Error message when you use SQL Server Management Studio to connect to SQL Server 2005 Integration Services from a client computer: «Connect to SSIS Service on machine ‘<SSISServer>’ failed Access is denied»

3.


When you try to connect to SQL Server Integration Services 2005 from SQL Server Management Studio, you may get below errors.

Error 1

Cannot connect to <computer-name>.

——————————

ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click:

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

——————————

Connect to SSIS Service on machine <computer-name> failed:

Error loading type library/DLL.

Error 2

Cannot connect to <computer-name>.

——————————

ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click:

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

——————————

Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80070005. (Microsoft.SqlServer.ManagedDTS)

Error 3

Cannot connect to <computer-name>.

——————————

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click:

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

——————————

ADDITIONAL INFORMATION:

Library not registered. (Exception from HRESULT: 0x8002801D

(TYPE_E_LIBNOTREGISTERED)) (Microsoft.SqlServer.DTSRuntimeWrap)

Causes and Resolutions

1.    Unregister and register DTS.dll.  If the SSIS is a 64-bit installation, unregister and register both 32-bit and 64-bit DTS.dll and  MsDtsSrvrUtil.dll files.  Commands are below.

Regsvr32 /u “C:Program Files (x86)Microsoft SQL Server90DTSBinnDTS.dll»

Regsvr32 /u “C:Program FilesMicrosoft SQL Server90DTSBinnDTS.dll»

Regsvr32 /u “C:Program Files (x86)Microsoft SQL Server90DTSBinn MsDtsSrvrUtil.dll»

Regsvr32 /u “C:Program FilesMicrosoft SQL Server90DTSBinn MsDtsSrvrUtil.dll»

Regsvr32 “C:Program Files (x86)Microsoft SQL Server90DTSBinnDTS.dll»

Regsvr32 “C:Program FilesMicrosoft SQL Server90DTSBinnDTS.dll»

Regsvr32 “C:Program Files (x86)Microsoft SQL Server90DTSBinn MsDtsSrvrUtil.dll»

Regsvr32 “C:Program FilesMicrosoft SQL Server90DTSBinn MsDtsSrvrUtil.dll»

This holds good for Error #1(Error loading type library/DLL.) and Error #3(TYPE_E_LIBNOTREGISTERE))

This error is encountered frequently when a Service pack is applied over an existing installation of Sql Server. During SP installation Sql automatically unregisters these dlls and on successful completion re-registers them. We have seen issues where the re-registration fails and Customer gets the above errors while connecting to SSIS after installation of a Service Pack.

2.    Unregister and register SqlTaskConnections.dll.  If the SSIS is a 64-bit installation, unregister and register both 32-bit and 64-bit SqlTaskConnections.dll files.  Commands are below.

Regsvr32 /u “C:Program Files (x86)Microsoft SQL Server90DTSBinn SqlTaskConnections.dll»

Regsvr32 /u “C:Program FilesMicrosoft SQL Server90DTSBinn SqlTaskConnections.dll»

Regsvr32 “C:Program Files (x86)Microsoft SQL Server90DTSBinn SqlTaskConnections.dll»

Regsvr32 “C:Program FilesMicrosoft SQL Server90DTSBinn SqlTaskConnections.dll»

3.    Make sure that the SSIS startup account has full permissions on folder

C:Program FilesMicrosoft SQL Server90DTSBinn where the SSIS binaries reside.

4.    Re-install Sql Server 2005 Client tools and Workstation Components.

Author : Deepak (MSFT) , SQL Developer Engineer , Microsoft

Reviewed by : Debarchan (MSFT) , SQL Developer Engineer , Microsoft