03-09-2016 08:18 AM - edited 03-09-2016 08:19 AM
Did you click the "Show details" button? Often this gives good insight as to what the underlyhing issue is. Please share that info with us.
03-09-2016 08:19 AM
What about checking "Show details"?
What kind of library is it?
It's not pre-assigned?
Does this happen for every user?
Search the metadata server & object spawner log for any more clues.
03-09-2016 09:22 AM
yes i checked with show details checkbox.
[Error] Error trying to establish connection: Unable to Initialize: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.
--------------------------- Technical Information Follows ------------------------------
SAS.EG.SDS.SDSException: <?xml version="1.0" ?><Exceptions><Exception><SASMessage severity="Error">Error trying to establish connection: Unable to Initialize: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.</SASMessage></Exception></Exceptions>
at SAS.EG.SDS.Model.Library.PopulateDatasets(Collection& collection)
at SAS.EG.SDS.Model.Broker.PopulateCollection(Collection collection)
at SAS.EG.SDS.Views.View.DoPopulate(DisplayOperation& op)
------------------------------ End of Technical Information -----
This issue is occuring for every user as Linush said..
thnx Linush & Jklaverstijn
03-09-2016 09:36 AM
Well there you have it. For some reason (many possibilities) you cannot get to the data in SQL Server as specified in the metadata. You will probably need to work with your trusted DBA to figure this one out. One hint I can give you:
Run this code from within EG. Insert the actual name of the library between the quotes:
libname test metalib library="<your library metadata name>" libdebug;
This will give you the current info used to assign the library from metadata.
Hope this helps,
03-10-2016 01:38 PM - edited 03-10-2016 01:40 PM
Try assigning a test LIBNAME without involving metadata. Does it work? If it does then your problem is with the metadata version. If it doesn't work then you need to get this right first before considering your metadata definition.
libname test "<your data library path>" ;
03-15-2016 06:30 AM - edited 03-15-2016 06:32 AM
We cannot provide a solution based on what we know. And it requires knowledge of your local installation. The best approach imho is still to run
libname test meta library="<your library metadata name>" libdebug;
Print out the log and take that to your local (database) support people.
03-10-2016 06:30 AM