|
Posted by Manuel Gomes on July 5, 2007, 9:00 am
If you were Registered and logged in, you could reply and use other advanced thread options
Hi
I have just downloaded FCS trial version to test, and i have installed
it in my system. The installation is done, after a few problems, and
FCS is running in the server. The problem appears when i try to run
the "Microsoft Forefront Client Security Console" - the first time you
run this a new "Before you begin" wizard starts that will condigure
the rest of FCS in the server - I enter all info requested (username,
reporting server urls etc), the 'Verifyings and Requirements' are 100%
ok but when i click next, entering the 'Completing the Configuration
Wizard' step, i get an error message in the 'Collection server
component' part, in the 'Reporting Server Adjustments' item. The error
message is 'Adjusts reports via Web service.' and the detail is the
following:
----- error detail begin -----
[05-07-2007 13:58:20] Task(Reporting Server Adjustments)
System.Web.Services.Protocols.SoapException:
System.Web.Services.Protocols.SoapException: The feature: "Report
caching" is not supported in this edition of Reporting Services. --->
Microsoft.ReportingServices.Diagnostics.Utilities.OperationNotSupportedException:
The feature: "Report caching" is not supported in this edition of
Reporting Services.
at
Microsoft.ReportingServices.Diagnostics.Sku.ThrowIfFeatureNotEnabled(String
instanceId, RestrictedFeatures feature)
at
Microsoft.ReportingServices.WebServer.ReportingService.SetCacheOptions(String
Report, Boolean CacheReport, ExpirationDefinition Expiration)
--- End of inner exception stack trace ---
at
Microsoft.ReportingServices.WebServer.ReportingService.SetCacheOptions(String
Report, Boolean CacheReport, ExpirationDefinition Expiration)
em
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean
asyncCall)
em
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
em
Microsoft.Forefront.ClientSecurity.Configure.ReportManagerWS.ReportingService.SetCacheOptions(String
Report, Boolean CacheReport, ExpirationDefinition Item)
em
Microsoft.Forefront.ClientSecurity.Configure.ReportServerAdjustmentTask.HideSubReports(ReportingService
rs)
em
Microsoft.Forefront.ClientSecurity.Configure.ReportServerAdjustmentTask.ReportServerTask()
em
Microsoft.Forefront.ClientSecurity.Configure.ReportServerAdjustmentTask.ThreadedWebServiceTask(Object
x)
----- error detail end -----
I am using an 1 server topology (all components of FCS installed) on
SBS 2003 Premium (SQL Server 2005 Workgroup edition)
MG
|
|
Posted by Manuel Gomes on July 5, 2007, 9:09 am
If you were Registered and logged in, you could reply and use other advanced thread options
In http://forums.microsoft.com/ForeFront/ShowPost.aspx?PostID=1763782&SiteID=41,
Mr Yaniv Feldman (Microsoft Security Regional Director) wrote: "sorry
to be the one with the bad news ... but FCS v1 doesn't support SBS
2003. FCS requires SQL Standard edition (SBS has SQL workgroup).".....
|
| Similar Threads | Posted | | Forefront Client Security | June 6, 2007, 1:07 pm |
| Error with Microsoft ForeFront Client Security | May 28, 2008, 10:28 am |
| Failed to config. Forefront client security on sbs2003r2 | July 22, 2008, 7:54 am |
| Problem with HTTPS client authentification | March 13, 2006, 3:30 pm |
| Microsoft Forefront Security for Exchange Server | February 27, 2007, 1:29 pm |
| VPN Client Security | August 29, 2008, 10:54 am |
| Novell VPN 3.8 Client and XP security privledges | June 24, 2005, 9:58 am |
| client OS security under Virtual PC 2007 | August 3, 2007, 12:34 pm |
| Problems with Forefront installation. | May 15, 2008, 2:54 pm |
| Forefront Managed Newsgroup | July 18, 2008, 9:12 am |
|
XML site map