10-23-2014 03:38 AM
I installed SAS 9.4 Data Management on a Windows Server 2008 R2 and SAS 9.4 Enterprise Guide 6.1 on a Client with Windows 7. After that I have checked all Servers and DI-Studio connection from a Client worked without problems.
Then I created a connection profile in the eGuide (used IWA) and tried to connect to the MetaData Server. When I marked the profile as an active profile I got the following message:
No Connection to the MetaData Server possible
Library not registered
Can somebody help me to solve this problem because I tried several things and nothing worked?
10-23-2014 04:23 AM
can you determine whether it is DLL (windows library) is failing or it is a SAS library (why?) that goes wrong.
It is strange as you did have connection with DI (java client) with that user and not with eguide (.Net).
10-23-2014 05:21 AM
No, there is no more information about the library in the error message.
I installed the eGuide not as an BI-Deployment but as a local Foundation installation.
In the SEGuide.register.log of this installation is a message
Could not load type library from C:\Program Files\SASHome 9.4\SASEnterpriseGuide\6.1\SASEGScripting.dll
10-23-2014 05:40 AM
You could google on SASEGScritping.dll it is a windows DLL and being expected on that location. I am guessing it is not there at hat location.
Either this is because of the way you did your installation, or there is something different. IT could be those dll's are added as part of the BI-deployment and not with the local foundation deployment.
There must be a MSI packge also (9.4 what is new). You must be able to talk with this information to SAS TS.
10-23-2014 07:14 PM
How about just trying a re-install of SAS EG to see if that helps? Or even try it on a different PC if there is one available.
10-29-2014 08:50 AM
I solved the problem. It was the fact that I installed the SAS eGuide via a local SAS Foundation. This installation has not all features which are necessary to work with the servers (meta data Server, workspace server etc.). I deinstalled the eGuide and installed it via a 2-Machine Deployment Plan on the server and on the client.
Now it works.
Thank you Jaap!! You turned me in the right direction.