EAC - Server Assembly File System Path

Our Production App is up and appears to be running fine, but there’s something in EAC that doesn’t look right. After connecting to an App, the Server Assembly File System Path value normally shows a path like:

image

That’s from our UAT (User Acceptance Testing App).

But the Production App shows:

image

It’s not actually blank, but rather a single dot(.). And if my DOS memory is correct, a single dot is the reference to “the current directory”, while the double dot (..) is the parent directory.

Any who … Really seems like this should set like all the others:

DEM_102300: C:\inetpub\wwwroot\DEM_102300\Server\Assemblies
UAT_102300: C:\inetpub\wwwroot\UAT_102300\Server\Assemblies
TST_102300: C:\inetpub\wwwroot\TST_102300\Server\Assemblies
PRD_102300_WUC: C:\inetpub\wwwroot\PRD_102300_WUC\Server\Assemblies

not

PRD_102300_WUC: .

Should I be concerned?

Not seeing that on our 102400 or 102600 environments. Have you tried redeploying the app? I know it’s your PROD environment so you’d have to do it off hours.

image

Slight fear that re-deploying it might break it. It’s currently in the “ain’t broke” status.

But seeing things like this are very disconcerting to me. I don’t even like seeing error messages in the Windows logs.

Yea… true. Could be a little “unstable” if you mess with it.

It must be right in the Epicor config or I don’t Epicor would run. I can’t remember where it’s at but there is a config file for EAC. I one time had a HTTP URL showing for an extension rather than the HTTPS link which is how it was deployed. Epicor Support had me modify a config file for the EAC and it fixed it. Wonder if this is a similar thing?

1 Like

The value displayed comes from the web.config appSettings node, specifically value AssemblyFileSystem.

Took me longer than I expected but at least I got to see some of the code of the admin console.

The Admin Console will show whatever value is specified in web.config what does your web.config have.

I compared web.config files for my production app (PRD_102300) and my test app (UAT_102300), and the only differences are anywhere “PRD_102300” is in the PRD app, it is “UAT_102300”.

Both have full paths in the AssemblyFileSystem keys

<add key="AssemblyFileSystem" value="C:\inetpub\wwwroot\UAT_102300\Server\Assemblies" />

and

<add key="AssemblyFileSystem" value="C:\inetpub\wwwroot\PRD_102300\Server\Assemblies" />

There’s regular server maintenance scheduled for this coming Saturday. I’ll see if it changes after the server is rebooted.