ES 7.0 Patch Update 5

Hi,

After the Patch Update5 installation there is a change in the display of the fileshare. Under the communications processes it just showas ccitcp *.*, but usually it shows with the ip address, port number, etc..

Hi Noel, to check does this actually affect the way e.g. file share works, is everything working ok?
Before the upgrade did you hard code an ip address and port, or did you change the way fileshare is started?

If this is urgent then please consider to raise a support case where one my colleagues can provide further assistance.

Hi Kim,

 to check does this actually affect the way e.g. file share works, is everything working ok? - doesnt looks like any issues, but need to observe.

 did you hard code an ip address and port, - No

did you change the way fileshare is started - No , nothing i can remember of.

If everything in terms of your application appears to be working then it would appear to be less critical, but to get an understanding of why you see the change I recommend you to:

-Confirm if any setting was changed pre/after the update, please verify, keep in mind this can include Windows configuration, did anything change there? Is is a different machine or the same machine?
-Raise a support case to seek help with understanding why the change is seen.

Hi Kim,

We have not done any changes at all. Just by instlaling the patch #5 we could see this difference then how can it be something else?

Please advice.

Hi Noel, do you experience/notice any issue with how your application works? I want to check if the chabge is causing any problem, or not.

If I recall correctly you may have made one change that is to enable anonymous access for mfds, can you confirm of that is correct?

Hi Kim,

i tried to connect to fileshare using fsview its connecting, able to get files and i am able to close the files also. But still i wonder how its going to be when its going to production, because there its going to be realtime

mfds anonymous acces thats is a different machine which only has es 7.0

So from an application view everything works which is good.

There must be a change to have caused this, you confirm nothing was changed, even on the Windows/OS side?

Yes there was no changes made.

I suggest you to raise a support case to seek help with understanding why the change is seen.

Hi Kim,

Just to update you that this behavious is seen from PU3 itself. But not in PU1 & 2.  I tried to isolate by installing different patch levels then i was able to conlude this.