1e NightWatchman 5.3

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

1e NightWatchman 5.3

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Vendor Forums] >> 1E Products >> 1e NightWatchman 5.3

Page: [1]

Message

<< Older Topic Newer Topic >>

1e NightWatchman 5.3 - 9/5/2008 4:04:43 PM

blaird

Posts: 7
Score: 0
Joined: 3/13/2006
Status: offline

We recently (8/27) purchased and started deploying the 1e products listed at the bottom of this post. I figured I'd open up this thread as a discussion of any issues/questions/resolutions that myself or others have encountered. I haven't yet contacted support, I figured I'd try the real-world folks on the MyITForum first! :-)

Issue: Not all reports working. Get a rather cryptic server error "Line 21: <add assembly="mscomctl, Version=10.0.4504.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>" on several reports.

Types of reports that are working (samples):

All the network Statistic
All the NightWatchman Performance
Daily Consumption, Total

Types of reports that are not working (samples):

All Cross Reference (Daily/Monthly)
All Emissions (Daily/Monthly)
Daily Organization Power Consumption

Oddly conspicious to me, the Daily Consumption Total works, but the Monthly Consumption Total doesn't. I figure if the CO2 or Cost reports don't work it may be related to missing something from the database. But it is obvious the Consumption data is in the database.

I have seen other folks post comments where it takes a couple cycles for the table data to get updated. I went into the SQL Enterprise Manager and kicked Hourly, Daily, and Weekly tasks (in that order) to ensure the data is getting populated. No luck!

Note: On the Wakeup, all reports are working except "highest failures", "server monthly", and "subnet monthly".

It's only been a week. Did I skip something in the documentation? Am I just being impatient? I'm open to thoughts and ideas!

Thanks,
Brian

Specs 1e:

AgilityFramework.v2.3.0.96
NightWatchman.v5.3.0.276
NightWatchman.ProductPack.v5.3.0.219
WakeUp.v5.5.1.166
WakeUp.ProductPack.v5.5.1.49
NomadBranch.v2.5.4.4

Specs SMS:

SMS 2003 SP2
Windows Server EE 2003 SP2
SQL Server 2000

Post #: 1

RE: 1e NightWatchman 5.3 - 9/5/2008 4:10:54 PM

regeter

Posts: 10
Score: 0
Joined: 10/26/2007
Status: offline

Hi Brian,

Sorry to tell you that I do actually work in Support @ 1E :)
However this is a known issue and I would like to ask you to download the newest AgilityFramework from our website.
AgilityFramework.v2.3.100.5

The product was referencing an ActiveX that was not actually included in the MSI of the version you have.
Regards,
Reto

(in reply to blaird)

Post #: 2

RE: 1e NightWatchman 5.3 - 9/5/2008 6:11:51 PM

blaird

Posts: 7
Score: 0
Joined: 3/13/2006
Status: offline

Hi Reto,

Talk about "bleeding edge"... the MSI and associated files were updated w/ an 11:50am time stamp today!

Downloaded and installed the AgilityFramework.v2.3.100.5. The links in question appear to be working now.

So far, everyone at 1E that I have met and worked with have all been very helpful and supportive. I won't hold it against you that you work for 1e! :-)

Thanks,
Brian

(in reply to regeter)

Post #: 3

RE: 1e NightWatchman 5.3 - 12/16/2008 3:36:37 PM

wshreeves

Posts: 2
Score: 0
Joined: 7/25/2008
Status: offline

We've recently begun rolling out NightWatchman to our production environment. While needing to troubleshoot an issue, I noticed that the NightWatchman.log logs are rolling over after hitting 62 KB instead of 1 MB even though it is set to 1048576 bytes, the default, as confirmed in the the registry value HKLM\SOFTWARE\1E\NightWatchman50\MaxLogFileSize. I intend to change the debug value from 9, the default, to 31 to help with troubleshooting and I wanted to make sure the logs would be large enough to retain at least a few days of history. Any suggestions as to why the logs are rolling over early?

(in reply to blaird)

Post #: 4

RE: 1e NightWatchman 5.3 - 12/18/2008 9:49:33 PM

wshreeves

Posts: 2
Score: 0
Joined: 7/25/2008
Status: offline

The log size has increased to 1MB on the handful of computers that I changed the debug level from 9 to 31 even though I didn't change the size from the default.

(in reply to wshreeves)

Post #: 5

RE: 1e NightWatchman 5.3 - 12/23/2008 3:44:07 PM

regeter

Posts: 10
Score: 0
Joined: 10/26/2007
Status: offline

Hi,

Yes, there is an issue with Debug levels that are "not supported", i.e strange values.
Debug 9 and 31 are both supported but if you, for instance had Debug Value 1 the issue you described would happen.
Are you sure it was set to Debug 9 at the time?
Reto

(in reply to wshreeves)

Post #: 6