cancel
Showing results for 
Search instead for 
Did you mean: 

BO4 - Windows event log messages - failed to determine status information

former_member272336
Participant
0 Kudos

Hi,

Despite folloiwng steps in sap notes

1771273 - Error "Failed to determine status information of

file/directory" found in System Events logs

1773822 - Failed to determine status information for file/directory

<Path\Filename>

we are seiing the messages detailed in the event log on these machines.

Admin user so can ruleout permissions - it has fullcontrol over the install and cache folders and sub-folders

Using bo4 sp6 2 node windows cluster.

Any other ideas?

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member182521
Active Contributor
0 Kudos

Hello Philip,

Could be a communication failure or Server outage. Could you share your event log entries?

Regards,

Mani

former_member272336
Participant
0 Kudos

Hi Mani,

messages below.

2 node cluster errors on both nodes.

sia running under and admin user - bothe servers on same domain no firewall or anti-virus sofwtare running - user concerned has full control on the folders and sub-folders on the cache + install dir

Failed to determine status information of file/directory C:\bocache\<node1>_6400\<node2>.WebIntelligenceProcessingServer1\sessions\_Aa0LWH2SnWpOm293qc77RR0\P0pi8452KT91{node2}{node2.WebIntelligenceProcessingServer1}{Aa0LWH2SnWpOm293qc77RR0}.tmp from the file system. Please check for file system corruption, permissions and sharing violation

Thanks

Former Member
0 Kudos

Does the error in Event logs give some issue in product functioning in any manner?

I suspect that the note 1773822 - Failed to determine status information for file/directory is valid to some extent.

Try to rename the node (4 letters such as Matt or phil )and see whether it helps.

former_member272336
Participant
0 Kudos

Hi,

No - no messages at front end.

Already followed the sap note concerned.

Now way under 260 charcaters.

Why would renaming node help?

Thanks

Former Member
0 Kudos

that was just to ensure we have small path length, however as you mentioned its less than 260. Short of clues

May be a silent trace of webi processing server would help to get us lead to what would be the issues with the messages to appear.

former_member272336
Participant
0 Kudos

Hi,

Have captured traces before and mentions ping server is down but can ping the servers no problem on command prompt and not manifesting itself in any messages at front end

thanks

Former Member
0 Kudos

If I am not wrong I believe its the CMS which does the pinging activity to the CMS Db along with availability of all services.(Need confirmation from experts in forum)

What does the health status tells us for CMS.

Can we have a look into the CMS logs

former_member272336
Participant
0 Kudos

cms shows as healthy nothing of interest in logs for cms - last time cms log entered into when the cms started

Raise previous question re these entries in cms log and assured fine.

M [Thr 5264] Fri Aug 16 04:00:11 2013

M  [Thr 5264] ***LOG Q0I=> NiPGetHostByName: '$SMDAgentHost' not found: getaddrinfo [ninti.c 895]

M  [Thr 5264] *** ERROR => Main agent failed to be initilized due to incorrect host setting! [ncsmtdatasen 20]

M  [Thr 5264] *** ERROR => Main agent failed to be initilized due to incorrect host setting! [ncsmtdatasen 20]

M  [Thr 5264] NCS trace timer is disabled since the interval is set to 0

M  [Thr 5264] NCS data timer is disabled since the interval is set to 0

M  [Thr 5264] NCS library version 2.3.9 (unicode) loaded

M  [Thr 5264] NCS_ProcInit API invoked

denis_konovalov
Active Contributor
0 Kudos

this ones are red herring. you can see them on healthy systems not configured for Solution manager.

Former Member
0 Kudos

Just curious to know whether the event log messages observed would also be reference to SMD. Either not installed or else incorrect installation.

former_member272336
Participant
0 Kudos

We haven't configure solution manager so not worried about the cms log messages.