Jump to content

Log Always Empty


SteveSBE

Recommended Posts

Michel -

 

I am using Win7 with Office 2007 and ISY99 2.8.4.

 

I repeated that test again. I saved it to a file and viewed the resulting text version of the log in Notepad. It is empty. Per Excel...I triple checked Excel and macros are enabled. But I'm more confused about why I don't see the log. BTW--I cleared the Java and browser cache and after a couple minutes looked at the log again...but that made no difference.

 

I don't know if this is related but I also get a "Failed to retrieving product update Information" when I open the Admin UI.

 

Thanks,

 

Steve

 

 

SteveSBE,

 

If you are using Windows Vista/7 with Office 2007-2010, then please do make sure that the MACROS are enabled. If not, you will see nothing in Excel. As a test, you could ask ISY not to show the logs in Excel and instead save it to a file.

 

With kind regards,

Michel

Link to comment

Rand -

 

I can see the following:

 

The "LS" command displays:

[/ *.*]

testfile.txt

queryall.isy

log

web

code

conf

user

tmp

 

The "LS log" command displays:

[/log *.*]

a.log 356966

b.log 1046528

c.log 1046528

error.log 137982

 

I'm not telnet proficent and don't know how to display the contents of the log file...

 

What else should I try?

 

Thanks,

 

Steve

 

 

You should certainly have log entries except for a short time after you select Clear Log.

 

If you Telnet to the ISY and issue LS LOG it should list several files with various sizes.

 

Rand

Link to comment

Thanks Michel. I assume the best way to schedule a call is to issue a support ticket...is that correct? (Sorry...I haven't used your support yet.). Thanks, Steve

 

Hi SteveSBE,

 

That is indeed quite odd since neither your error log nor your log is empty (based on the output of the telnet).

 

I think the best thing to do would be to have a support call scheduled so that we can see what's going on.

 

With kind regards,

Michel

Link to comment

Michel,

 

Before I set up a support call, I tried to view my log using Firefox and OpenOffice on my MacBook Pro to eliminate any issues with the ISY99. I DID get a log file to display...with data in it!

 

So I suspect this problem is unique to Windows 7 (Ultimate) since I don't see the log in either a text file using Notepad nor in Excel. Just for kicks, I disabled the antivirus and firewall and tried it again but had the same results.

 

Is there anything else you'd like be to try before scheduling a call?

 

Thanks,

 

Steve

 

 

Hi SteveSBE,

 

That is indeed quite odd since neither your error log nor your log is empty (based on the output of the telnet).

 

I think the best thing to do would be to have a support call scheduled so that we can see what's going on.

 

With kind regards,

Michel

Link to comment

When asked if I want to view the log in Excel, I select NO. It prompts me where to save the log and I save it to my desktop. It looks like the ISY version and file date/time are used in the naming conventions for the log file (e.g. ISY Log.v2.8.4__2010-10-24.11.54.33.txt).

 

Thanks,

Steve

 

Hi Steve,

 

Thanks for the update.

 

So, to be clear, when you are asked whether or not you want to view the log in Excel, do you choose NO? If so, do you actually see where the log is saved?

 

With kind regards,

Michel

Link to comment
  • 2 weeks later...

Michel,

 

Thanks...I've been busy and haven't had time to call but may later today.

 

Maybe this will help....

The Java Console log created this entry when I clicked on Tools/Log:

cache: Reading Signers from 1485 http://192.168.0.5/web/chart.jar | C:\Users\Steve\AppData\LocalLow\Sun\Java\Deployment\cache\6.0\59\cec81bb-3776c50c.idx

 

I looked in the folder above and these are the entries in that folder:

http://screencast.com/t/rE1cRr0qIA

 

The information doesn't display in either the text file or in the Excel file on my Win7 PC (even when both the firewalls and antivirus are off).

 

I can view the information in both text and .xml formats if I do the same think on my MacBook Pro (and get a log file that is a few hundred lines long).

 

I think it has to do with a setting in Windows 7. I'm running Win7 64 bit. Could that be an issue?

 

I'll try to call later today.

 

Thanks,

 

Steve

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...