Desktop productivity for business analysts and programmers

Connectivity error to SAS EG

Occasional Contributor
Posts: 5

Connectivity error to SAS EG

Hello SAS Gurus -

One of the user is getting below message when he is trying to setup profile for his Id in SAS EG 4.1 and below is the error message, I'm not sure what the error is?

Please note that I verified the connection properties and they are correct. Please let me know if you face the same problem earlier or know the reason for not able to connect.

Thanks in advance.

A connection could not be made to the SAS Metadata Server but is required for the current operation. Please see your administrator.


Connection failed

------------------------------ Technical Information Follows ------------------------------

SAS.EG.SDS.Metadata.MetadataException: Connection failed ---> System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {D6979A27-6B31-11D5-BA37-00C04F81BC00} failed due to the following error: 80040154.

   at SAS.EG.SDS.Metadata.OMSProvider.Connect()

   --- End of inner exception stack trace ---

   at SAS.EG.SDS.Metadata.OMSProvider.Connect()

   at SAS.EG.SDS.Metadata.MetadataManagerV2.SAS.EG.SDS.Metadata.IMetadataConfiguration.set_ActiveProvider(Provider value)

   at SAS.EG.SDS.Dialogs.ProviderConnectDlg.Connect(Object sender, DoWorkEventArgs e)

   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)

   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

------------------------------ End of Technical Information ------------------------------

Trusted Advisor
Posts: 2,114

Re: Connectivity error to SAS EG

This one probably warrants opening a ticket with Tech Support.

Super User
Posts: 3,233

Re: Connectivity error to SAS EG

The first question to ask here is: has EG worked OK on this PC before this error started happening or is this the first time the user has tried to use EG on this PC?  A reinstall in both cases would do no harm and it might be quicker than troubleshooting.

Ask a Question
Discussion stats
  • 2 replies
  • 3 in conversation