topic Re: SAS Environment Manager ".DCOM: application-specific! in Administration and Deployment

SAS Environment Manager ".DCOM: application-specific!

FK1 — Fri, 26 Jun 2020 08:47:01 GMT

Hello Everyone,

I an completely new to the handling of the SAS Environment Manager. I do have the following problem:

I can see from our SQL Database log, which runs on server X, that there are regular unsuccessful attempts of the SASDEMO-User to log onto our database, which originate from our SAS compute server, which runs on server Y. I know, that they originate from server Y, because the database log shows the "CLIENT: IP-Adress" , which is the one from server Y.

When checking the times in the SQL Server Log, I can see that they exactly correlate to ERROR-Events in the Environment Manager:

My question is: how can I turn of these attempts?
How are they generated in the first place?

Any help would be very much appreciated.

Cheers,

Re: SAS Environment Manager ".DCOM: application-specific!

AnandVyas — Fri, 26 Jun 2020 08:58:28 GMT

How does SAS connect to the DB? Is there pre-defined library definition created in SMC?

It could be that the library is pre-assigned which means every time a SAS session is spawned it would try to create a connection and probably sasdemo isn't part of the auth doman or group to make it work.

Re: SAS Environment Manager ".DCOM: application-specific!

FK1 — Fri, 26 Jun 2020 11:07:42 GMT

Hi Anand_V,

yes, I set up a Pre-Assigned Library in SMC which connects to the SQL Database.

But I do not belive, that your assumption that "every time a SAS session is spawned it would try to create a connection." is probable, since only at exactly the full hour this attempt of sasdemo-user is made.....

Re: SAS Environment Manager ".DCOM: application-specific!

AnandVyas — Fri, 26 Jun 2020 11:34:09 GMT

Is this library assigned successfully when a SAS session is launched by user sasdemo?

Re: SAS Environment Manager ".DCOM: application-specific!

FK1 — Fri, 26 Jun 2020 12:30:38 GMT

No, because this account is not allowd to do anything on the database!

libname DATAMART sqlsvr schema='SAS_DATAMART' INSERTBUFF=32767 READBUFF=32767 DBCOMMIT=0 Datasrc=SAS_ACCESS_TREIBER ;

Log tells correctly:

ERROR: CLI error trying to establish connection: [SAS][ODBC SQL Server Wire Protocol driver]Socket closed. : [SAS][ODBC SQL Server
Wire Protocol driver][SQL Server]Login failed for user 'KKEU\sasdemo'. Reason: The account is disabled.
ERROR: Error in the LIBNAME statement.

For testing reasons, what ecactly happens, I granted sasdemo for a short period of time access to the database. The SQL-server log then tells me, that sasdemo queries the field types of the database and also checks its own username:

But the question remains: why does it do this? Who tells sasdemo to query the database?

Re: SAS Environment Manager ".DCOM: application-specific!

gwootton — Fri, 26 Jun 2020 13:27:43 GMT

It is possible to configure Environment Manager to validate the Workspace Server at regular intervals. If this has been done and using the sasdemo user, it would explain why this attempt is happening every hour.

You could deny sasdemo ReadMetadata permission on the library in SAS Management Console to prevent the Workspace Server from attempting and failing to assign it by way of pre-assignment each time the validation occurs.

Re: SAS Environment Manager ".DCOM: application-specific!

AnandVyas — Fri, 26 Jun 2020 13:57:23 GMT

If this happens every hour from a SAS session spawned by sasdemo its also possible to enable workspace server session logs to see which process is trying to make a connection every hour.

Re: SAS Environment Manager ".DCOM: application-specific!

FK1 — Mon, 29 Jun 2020 12:01:50 GMT

Good idea! Thank's for the hint!