End tag 'object' does not match the start tag page

Management reporting and documentation

End tag 'object' does not match the start tag page

Veeam Logoby aelitadan » Wed Apr 11, 2007 5:38 pm

I am running WIN2K3 Standard Edition Server SP2 on a VMware ESX 3.x server. I have installed the most recent version of Reporter and a trial copy of VISIO 2007. Reporter connects fine to the ESX server but ends with a dialog box with a similar message to the one in RED below. VISIO opens but there is no data (blank visio window). Below is the log that is generated by Reporter:

4/11/2007 7:12:17 AM - Connecting to xx.xxx.x.x as dsmith
4/11/2007 7:12:25 AM - Enumerating objects
4/11/2007 7:12:25 AM - Enumerating Network
4/11/2007 7:12:25 AM - Enumerating objects: Network
4/11/2007 7:12:41 AM - Enumerating Storage
4/11/2007 7:12:41 AM - Enumerating objects: Storage
4/11/2007 7:12:42 AM - Enumerating Configuration
4/11/2007 7:12:42 AM - Enumerating objects: Configuration
4/11/2007 7:12:46 AM - Writing the configuration settings to XML file
4/11/2007 7:12:46 AM - Generating Visio diagram using the XML file
4/11/2007 7:12:46 AM - Initializing generator
4/11/2007 7:12:48 AM - Reading XML
4/11/2007 7:12:48 AM - End tag 'object' does not match the start tag 'page'.
4/11/2007 7:12:48 AM - Reading XML
4/11/2007 7:12:48 AM - GUID: {00000000-0000-0000-0000-000000000000}
SOURCE:
MESSAGE:
ACTION: 10
aelitadan
Novice
 
Posts: 7
Liked: never
Joined: Sun Jan 01, 2006 1:01 am

Veeam Logoby vmadmin » Thu Apr 12, 2007 11:59 am

This may happen when your user doesn't have read rights for some objects at ESX. Try to re-assign read rights for the ESX node and don't forget to check "propagate" option.
vmadmin
Enthusiast
 
Posts: 73
Liked: never
Joined: Sun Jan 01, 2006 1:01 am

Veeam Logoby aelitadan » Fri Apr 13, 2007 5:09 pm

I have limited permissions on the ESX server. It is managed by another group. However, I do have Read permissions on two server images. Shouldn't I get some data from those objects? I currently get a blank VISIO diagram and the error in the log.

Originally posted by vmadmin

This may happen when your user doesn't have read rights for some objects at ESX. Try to re-assign read rights for the ESX node and don't forget to check "propagate" option.
aelitadan
Novice
 
Posts: 7
Liked: never
Joined: Sun Jan 01, 2006 1:01 am

Veeam Logoby vmadmin » Wed Apr 25, 2007 3:38 pm

You should have Read permissions for the ESX with the propagate option checked.
vmadmin
Enthusiast
 
Posts: 73
Liked: never
Joined: Sun Jan 01, 2006 1:01 am

Veeam Logoby aelitadan » Wed May 16, 2007 8:15 pm

I have all the correct permissions now and the product is working 100%. Looking forward to the next version with new output formats.

Originally posted by vmadmin

You should have Read permissions for the ESX with the propagate option checked.
aelitadan
Novice
 
Posts: 7
Liked: never
Joined: Sun Jan 01, 2006 1:01 am


Return to Reporting



Who is online

Users browsing this forum: No registered users and 3 guests