Answered by:
Error when Importing Organization (The requested name is valid, but no data ....)

Question
-
Hello Forum,
i am trying to import an Organization which we restored from a backup. But we get a SQL Error:
"The requested name is valid, but no data of the requested type was found"
The SQL Server is installed in a cluster with a named instance.
When we try to import everything works fine.... the Deployment Manager recognizes the Org Database, then we map the users.
But when the System Check runs we get the error above.
Any ideas?
Wednesday, February 8, 2012 8:25 AM
Answers
-
Since it is a SQL error I would say you should try to run SQL Profiler on the SQL box while you are performing the operation along with CRM Tracing to see if you get better info when it fails next time.
http://crmdiagtool2011.codeplex.com/
Jamie Miley
Check out my about.me profile!
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!- Marked as answer by Jamie MileyModerator Monday, September 17, 2012 2:15 PM
Monday, February 13, 2012 3:38 PMModerator -
There should be a log file from deployment manager. If you check Users\<Username>\AppData\Roaming\MSCRM you will should get more detail about the error. I'm assuming this check comes up on the SQL Server line item in the System Check? This used to be caused by DNS issues or problems resolving the named instance, or it's resolving but returning back a specific node in the cluster rather than the cluster itself.
Probably worth doing as Jamie suggested to see if the connection attempt is even registering.
Jeremy
Jeremy Winchell
Avtex
Visit the Avtex Blog- Marked as answer by Jamie MileyModerator Monday, September 17, 2012 2:15 PM
Thursday, February 16, 2012 12:36 AM -
I agree that it sounds like a name resolution issue, but CRM does seem to have problems importing organisations in some high-availability SQL configurations.
This may or may not be helpful, but we recently had this error on a mirrored SQL Server, and the resolution was to remove the 'Failover Partner' component of the SQL connection (which is in the registry at HKLM\Software\Microsoft\MSCRM\configdb).
What is your connection string in the confibdb registry value ?
Microsoft CRM MVP - http://mscrmuk.blogspot.com http://www.excitation.co.uk
- Edited by DavidJennawayMVP, Moderator Thursday, February 16, 2012 8:25 AM
- Marked as answer by Jamie MileyModerator Monday, September 17, 2012 2:15 PM
Thursday, February 16, 2012 8:25 AMModerator
All replies
-
Since it is a SQL error I would say you should try to run SQL Profiler on the SQL box while you are performing the operation along with CRM Tracing to see if you get better info when it fails next time.
http://crmdiagtool2011.codeplex.com/
Jamie Miley
Check out my about.me profile!
http://mileyja.blogspot.com
Linked-In Profile
Follow Me on Twitter!- Marked as answer by Jamie MileyModerator Monday, September 17, 2012 2:15 PM
Monday, February 13, 2012 3:38 PMModerator -
Hi Hurrikane1982,
Try importing the organisation with the SQL server IP address instead of the Server name.
Let us know if that helped.
Regards
Nuno
Visit my blog for CRM material, improving performance, kerberos, IFD, development tips, etc. :) http://quantusdynamics.blogspot.com
Tuesday, February 14, 2012 9:07 PMAnswerer -
There should be a log file from deployment manager. If you check Users\<Username>\AppData\Roaming\MSCRM you will should get more detail about the error. I'm assuming this check comes up on the SQL Server line item in the System Check? This used to be caused by DNS issues or problems resolving the named instance, or it's resolving but returning back a specific node in the cluster rather than the cluster itself.
Probably worth doing as Jamie suggested to see if the connection attempt is even registering.
Jeremy
Jeremy Winchell
Avtex
Visit the Avtex Blog- Marked as answer by Jamie MileyModerator Monday, September 17, 2012 2:15 PM
Thursday, February 16, 2012 12:36 AM -
I agree that it sounds like a name resolution issue, but CRM does seem to have problems importing organisations in some high-availability SQL configurations.
This may or may not be helpful, but we recently had this error on a mirrored SQL Server, and the resolution was to remove the 'Failover Partner' component of the SQL connection (which is in the registry at HKLM\Software\Microsoft\MSCRM\configdb).
What is your connection string in the confibdb registry value ?
Microsoft CRM MVP - http://mscrmuk.blogspot.com http://www.excitation.co.uk
- Edited by DavidJennawayMVP, Moderator Thursday, February 16, 2012 8:25 AM
- Marked as answer by Jamie MileyModerator Monday, September 17, 2012 2:15 PM
Thursday, February 16, 2012 8:25 AMModerator