Endpoint Protection

Hi all,

 

I set up the Rerporting Sever service in our SAV 10.1.6.x environment. Everything looks good. However, I obtain no data at all. I wonder if I missed something. By the way, we have several different server groups and each one has different username and password to lock or unlock the SSC. The sa account for our SQL also has different password. Is that the problem? Thanks in adavnce.

 

Vince 

I'm running 10.1.7 and having the same issue on 2 different Reporting Servers. I can log into the Reporting Server just fine. There is simply no data to report. Any help would be greatly appreciated.

Did you install the reporting server agent? and point to the reporting server?

You need to install the reporting server agent on the server where you have ssc and then configure it to point to the reporting server url.

Hi,

Remember to configure reporting server in your group primary settings. It will distribute the settings to all the secondaries in the server group.

- Jukka

The reporting agent is installed. I verified that it is running. I configured the group settings to point to the reporting server. I don't have any secondary servers in the group...just the one primary. I see the graphs and charts, there just isn't any data reflected in them.

I'm sure I've missed something simple here. I'm just not seeing it.

Thanks again!

Hi,

Events should flow in through C:\Program Files\Symantec\Reporting Server\Upload so there should be constantly some files coming in. Which database are you using? Try to open the database with some admin tools to see what is stored in it if anything.

- Jukka

I'm using MySql. There is nothing at all in the Upload directory.

I tried to reinstall Reporting Server, unfortunately the server is at a remote site antd it won't let me install over RDP.

What are the status of the agents on the Reporting Server page? Is it hanging? How far apart are the Servers? Can you give some more info/background on your setup?

OK,

I haven't tried using reporing server with MySQL and there's nothing about MySQL in documentations, so I guess it's not supported. What if you would just install reporting server with MSDE?

- Jukka

MySQL isnt supported.

MSSQL however is, be aware tho there is a 2gb db limit with MSDE; If you have access to a SQL Server 2000 + id reccomend using that, especially if you have a large client base.

Couple of things.

Your reporting server url should be:

http://<server ip/fqdn>/reporting/

Right click your Perant Group > All tasks > Reporting Configuration > Configure Reporting Server

Put the URL you use to connect to the dashboard into the box and OK, you should get logs within 30 minutes.

MS SQL 2005 Express Edition is limited to 4GB as opposite to MSDE 2 GB limit.

You should use the Reporting server with MSDE. but has only 2GB limit.

Hi,

Database for 50000 clients is under usually 1GB, so I guess MSDE should not be a problem. Of course it has also other limitations compared to full versions of SQL, Same goes for SQL 2005 Express, for example it can only use 1 processor and 1GB of RAM.

- Jukka

I apologize for my earlier braindead reply. I'm running reporting server on a 2nd instance of MSDE. MS SQL 8. Not MY SQL.

Hi,

I saw issues with MSDE so swithed to SQL 2005 Express. Maybe you could try that. http://msdn.microsoft.com/en-us/library/ms345154.aspx

- Jukka

Ok, i think we might be going off the beaten track slightly here.

Can you go into the following:

C:\Windows\System32\LogFiles\W3SVC1

Open up your latest log file, chances are you wont see the following line:

2009-04-16 23:06:44 W3SVC1 10.64.118.137 POST /reporting/admin/upload.php - 80 - 19.103.103.250 libwww-perl/5.803 200 0 0

Last 2 questions :)

Are you able to go to the following URL:

http://ReportingServerIP/reporting/admin/upload.php

You should be presented with a Blank Page. If not and you are challenged to supply Windows Credentials it is then your IIS config and more specifically your IUSR_<ServerName>

Can you paste up the last lines of your latest W3SVC1 Log file so we can see whats going on.

Thanks,

Last few lines of the log file:

2009-04-17 14:24:38 W3SVC1 192.168.x.xxx POST /Reporting/admin/upload.php - 80 - 192.168.x.xxx libwww-perl/5.803 401 1 0
2009-04-17 14:25:38 W3SVC1 192.168.x.xxx POST /Reporting/admin/upload.php - 80 - 192.168.x.xxx libwww-perl/5.803 401 1 0
2009-04-17 14:26:38 W3SVC1 192.168.x.xxx POST /Reporting/admin/upload.php - 80 - 192.168.x.xxx libwww-perl/5.803 401 1 0

When I hit the url (http://ReportingServerIP/reporting/admin/upload.php), I was prompted for Windows credentials.

Note: The 2 servers I'm having problems with are both domain controllers at remote sites...the only server at those sites. SAV, AMS and Reporting Server are all running on this same machine.

Thank you.

The above is what i had a feeling you would see.

401 Unauthorised.

2009-04-17 14:26:38 W3SVC1 192.168.x.xxx POST /Reporting/admin/upload.php - 80 - 192.168.x.xxx libwww-perl/5.803 401 1 0

Can you make sure that in iis that your reporting site has Anonymous access enabled, with Integrated Authentication Disabled. Make sure that your anonymous account is your USR_<Servername> also make sure this account is not a member of Guests and is a Member of Users.

Is your reporting server a Domain Controller also ?

Reporting site has Anonymous access enabled. Integrated Authenticaion is disabled. My anonymous account is IUSR_<servermame> and is a meber of Guests. I'll remove that and see if things start logging.

Yes, the reporting server is a DC.

Thank you for your help.

Mr. O'Brien, I can't thank you enough for your help. Reporting is working as it should be. Thank you for your help!

Hi Julie,

No problem! Glad i could of been of assistance!

I have the same problem and I tried all of the above solutions but the problem still exists.

Hi binayak, no data on your reporting server dashboard? Can you give a background on what steps you have done after installing the reporting components? (e.g. config, etc.)

Yes, nothing is displayed on the dashboard. For your information I installed MSDE with the Reporting Server.

I configuring a server group to use the reporting server.

I did the following steps:

1 . Start the Symantec System Center and unlock the server group that contains the computer that runs the reporting server.
2.  On the Tools menu, click Discovery Service.

3.  In the Discovery Service Properties dialog box, on the General tab, under Cache Information, click Clear Cache Now, and then click Close.

4.  Unlock the server group.

5.  Right-click on the server group, and then click All Tasks > Reporting Configuration > Configure Reporting Server.
In the Reporting Server Options dialog box, select the reporting server that you installed, and then click OK.
 

Hi, have you also installed reporting server agent, this will collect the data on SAV server..

Hi,

Reporting server can only be configured on server group level if all the servers in that group have agent installed, so agents are most likely installed. If you look in C:\Program Files\Common Files\Symantec Shared\Reporting Agents\Win32, you can see LogReaderEvents_<Date>.log and also other log files. Look inside those to see why it's not working.

- Jukka

Hi,

I'm having intermittent issues with my Reporting server. The webpage is displaying a white blank screen,
however, the reporting server will be fine after a reboot, and then after several days, the page will be unaccessible again with a blank screen.
hope someone can help. I don't wish to be rebooting the server every few days

Can you double check size of Reporting.mdf file? Its under c:\Program Files\MSSQL\

Could it just be CGI timeout, if something is taking up resources a couple of days after reboot and the homepage of reporting will do large queries is database. It's normally much faster anyways to start with something else than homepage, like http://<servername>/reporting/admin/agentstatus.php for example.

- Jukka

Hi,

I've the same problem with my reporting server : The webpage is displaying a white blank screen.
I have a MSDE Database with size limit to 2Go. My reporting database has reached this size...I've migrated from MSDE to SQL Server Express to turn around the issue (The Express version has a 4Gb database limitation) but nothing changes !!!!

hope someone can help...please...

Hi you have to increase the transaction log first.

Hi Paul,

Can i increase transaction log after SQL Server Express migration or it's too late ?
Nb.: After migrating to Express Edition i saw that reporting database was on a 'Stopped, Normal' state. I think that the stopped state was due to db size (2Go) and i truncate some tables to free some spaces. After truncate => the database was on a 'normal' state but when i try to connect to the reporting server the webpage is still blank!!!!

Thx

Have you checked the db for corruption?

Hi all.

I have one primary server and 9 secondary servers of SAV 10.1.6 can i generate all client and server updation report from one console.if it is possible than how can i do that.Plz suggest solution or url to get the related information.