SharePoint Addin For Reportingservice

Mar 13, 2007

Hi,

I have a security problem (?) with the integration of sharepoint and Reporting service:

Now I have 2 server,

One with windows server 2003 Enterpise edition with share point services 3.0, I have installed the addin in this server

One with Windows Server 2003 with Sql Server 2005 sp2.

I have configured the reporting server to use a new db in Sharepoint integrated mode, the windows service identity, web service identity, the execution account and the db credential use a windows credential and use a domain user. This user is an administrator in the sharepoint server and in the Sql server. The user have the grand in the sharepoint db and in the Reoprting service db (db_owner).

The connection pool for Sharepoint is running under a domain account identity and the connection pool of the reporting service is running under network service.

After that I have configured the manage integration setting (Windows Authentication) and the Grant database acces using the same domain user configured for Reporting service.

My user have the db_owner grant for the db of sharepoint and reporting service.

When i click on Set server default I receve this error:

The permissions granted to user '<domain><user>' are insufficient for performing this operation. ---> The permissions granted to user '<domain><user>' are insufficient for performing this operation.

My user is administraton in the sharepoint server and in the Sql server.

the log in the reporting service is:

w3wp!library!1!03/13/2007-14:42:04:: v VERBOSE: Transaction begin.
w3wp!security!1!03/13/2007-14:42:04:: i INFO: Exception while running with elevated privileges
w3wp!security!1!03/13/2007-14:42:04:: i INFO: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
w3wp!library!1!03/13/2007-14:42:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.SharePointException: Report Server has encountered a SharePoint error.
w3wp!library!1!03/13/2007-14:42:04:: v VERBOSE: Transaction rollback.
w3wp!runningrequests!1!03/13/2007-14:45:04:: v VERBOSE: SoapAction: "http://schemas.microsoft.com/sqlserver/2006/03/15/reporting/reportingservices/ListSecureMethods"
w3wp!runningrequests!1!03/13/2007-14:45:04:: v VERBOSE: SoapAction: "http://schemas.microsoft.com/sqlserver/2006/03/15/reporting/reportingservices/GetSystemProperties"
w3wp!library!1!03/13/2007-14:45:04:: Call to GetSystemPropertiesAction().
w3wp!library!1!03/13/2007-14:45:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user '<domain><user>' are insufficient for performing this operation., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user '<domain><user>' are insufficient for performing this operation.
w3wp!security!1!03/13/2007-14:45:04:: i INFO: Exception while running with elevated privileges
w3wp!security!1!03/13/2007-14:45:04:: i INFO: The permissions granted to user '<domain><user>' are insufficient for performing this operation.
w3wp!library!1!03/13/2007-14:45:04:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user '<domain><user>' are insufficient for performing this operation., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.AccessDeniedException: The permissions granted to user '<domain><user>' are insufficient for performing this operation.

Please, could someone help me?


View 13 Replies


ADVERTISEMENT

SQL2005 SP2 Dec CTP Sharepoint AddIn Install Problem

Jan 22, 2007

Hi,



I've installed the Dec CTP of SP2 on a Windows Server 2003 SP1 virtual machine. Sharepoint and SQL2005 are running on the same machine. It currently has 1GbRAM allocated.

I configured the Report Server to use a Sharepoint integrated report server database. (Missed this first time round).

Then I installed the SharepointRS.msi.

I see no sign of the Reporting Services section in Central Administration, Application Management, and in Central Administration>Site Settings>SiteFeatures, I see no sign of Reporting Services either.

Below is the log file from SharepointRS.msi /l*

Any help much appreciated.

Thanks

Martin

=== Logging started: 22/01/2007 14:54:20 ===
Action 14:54:20: INSTALL.
Action start 14:54:20: INSTALL.
Action 14:54:20: ProgramFilesFolder.BB9BCD10_C507_4374_A5FC_3F04C705A420.
Action start 14:54:20: ProgramFilesFolder.BB9BCD10_C507_4374_A5FC_3F04C705A420.
Action ended 14:54:20: ProgramFilesFolder.BB9BCD10_C507_4374_A5FC_3F04C705A420. Return value 1.
Action 14:54:20: LaunchConditions. Evaluating launch conditions
Action start 14:54:20: LaunchConditions.
Action ended 14:54:20: LaunchConditions. Return value 1.
Action 14:54:20: FindRelatedProducts. Searching for related applications
Action start 14:54:20: FindRelatedProducts.
Action ended 14:54:20: FindRelatedProducts. Return value 1.
Action 14:54:20: IsPendingRebootKey.
Action start 14:54:20: IsPendingRebootKey.
PendingFileRenameOperations contains:
??C:Documents and SettingsAll UsersApplication DataNetwork AssociatesCommon FrameworkUpdateDir~~
No file in package listed in PendingFileRenameOperations
Action ended 14:54:22: IsPendingRebootKey. Return value 1.
Action 14:54:22: SetupInitializationDlg.
Action start 14:54:22: SetupInitializationDlg.
Info 2898.Tahoma8, Tahoma, 0
Info 2898.DlgTitleStyleB, Tahoma, 0
Action 14:54:22: SetupInitializationDlg. Dialog created
Action ended 14:54:22: SetupInitializationDlg. Return value 1.
Action 14:54:22: AppSearch. Searching for installed applications
Action start 14:54:22: AppSearch.
AppSearch: Property: REDISTINSTALLEDVERSION, Signature: Redist_VersionRegKey
AppSearch: Property: RSSPTARGETDIR, Signature: RSSPTargetDirLocator
Action ended 14:54:22: AppSearch. Return value 1.
Action 14:54:22: CCPSearch. Searching for qualifying products
Action start 14:54:22: CCPSearch.
Action ended 14:54:22: CCPSearch. Return value 0.
Action 14:54:22: RMCCPSearch. Searching for qualifying products
Action start 14:54:22: RMCCPSearch.
Action ended 14:54:22: RMCCPSearch. Return value 0.
Action 14:54:22: ValidateProductID.
Action start 14:54:22: ValidateProductID.
Action ended 14:54:22: ValidateProductID. Return value 1.
Action 14:54:22: CostInitialize. Computing space requirements
Action start 14:54:22: CostInitialize.
Action ended 14:54:22: CostInitialize. Return value 1.
Action 14:54:22: FileCost. Computing space requirements
Action start 14:54:22: FileCost.
Action ended 14:54:22: FileCost. Return value 1.
Action 14:54:22: IsolateComponents.
Action start 14:54:22: IsolateComponents.
Action ended 14:54:22: IsolateComponents. Return value 0.
Action 14:54:22: CostFinalize. Computing space requirements
Action start 14:54:22: CostFinalize.
Action ended 14:54:22: CostFinalize. Return value 1.
Action 14:54:22: IsDotNet20Installed.
Action start 14:54:22: IsDotNet20Installed.
Feature SharepointRS install action does not match 2.
Not all features are being removed.
One or more .NET Framework assemblies found in MsiAssembly table require the GAC, need to check for the .NET Framework
Action ended 14:54:23: IsDotNet20Installed. Return value 1.
Action 14:54:23: CA_SetARPINSTALLLOCATION.
Action start 14:54:23: CA_SetARPINSTALLLOCATION.
Action ended 14:54:23: CA_SetARPINSTALLLOCATION. Return value 1.
Action 14:54:23: MigrateFeatureStates. Migrating feature states from related applications
Action start 14:54:23: MigrateFeatureStates.
Action ended 14:54:23: MigrateFeatureStates. Return value 0.
Action 14:54:23: InstallWelcomeDlg.
Action start 14:54:23: InstallWelcomeDlg.
Action 14:54:23: InstallWelcomeDlg. Dialog created
Info 2898.DlgTextStyleB, Tahoma, 0
Action 14:54:25: LicenseAgreementDlg. Dialog created
Action 14:54:28: CustomerInfoDlg. Dialog created
Action 14:54:29: ReadyToInstallDlg. Dialog created
Action ended 14:54:30: InstallWelcomeDlg. Return value 1.
Action 14:54:30: SetupProgressDlg.
Action start 14:54:30: SetupProgressDlg.
Action 14:54:30: SetupProgressDlg. Dialog created
Action ended 14:54:30: SetupProgressDlg. Return value 1.
Action 14:54:30: ExecuteAction.
Action start 14:54:30: ExecuteAction.
Action 14:54:30: INSTALL.
Action start 14:54:30: INSTALL.
Action 14:54:30: ProgramFilesFolder.BB9BCD10_C507_4374_A5FC_3F04C705A420.
Action start 14:54:30: ProgramFilesFolder.BB9BCD10_C507_4374_A5FC_3F04C705A420.
Action ended 14:54:30: ProgramFilesFolder.BB9BCD10_C507_4374_A5FC_3F04C705A420. Return value 1.
Action 14:54:30: LaunchConditions. Evaluating launch conditions
Action start 14:54:30: LaunchConditions.
Action ended 14:54:30: LaunchConditions. Return value 1.
Action 14:54:30: FindRelatedProducts. Searching for related applications
Action start 14:54:30: FindRelatedProducts.
Action ended 14:54:30: FindRelatedProducts. Return value 0.
Action 14:54:30: IsPendingRebootKey.
Action start 14:54:30: IsPendingRebootKey.
PendingFileRenameOperations contains:
??C:Documents and SettingsAll UsersApplication DataNetwork AssociatesCommon FrameworkUpdateDir~~
No file in package listed in PendingFileRenameOperations
Action ended 14:54:31: IsPendingRebootKey. Return value 1.
Action 14:54:31: AppSearch. Searching for installed applications
Action start 14:54:31: AppSearch.
Action ended 14:54:31: AppSearch. Return value 0.
Action 14:54:31: CCPSearch. Searching for qualifying products
Action start 14:54:31: CCPSearch.
Action ended 14:54:31: CCPSearch. Return value 0.
Action 14:54:31: RMCCPSearch. Searching for qualifying products
Action start 14:54:31: RMCCPSearch.
Action ended 14:54:31: RMCCPSearch. Return value 0.
Action 14:54:31: ValidateProductID.
Action start 14:54:31: ValidateProductID.
Action ended 14:54:31: ValidateProductID. Return value 1.
Action 14:54:31: CostInitialize. Computing space requirements
Action start 14:54:31: CostInitialize.
Action ended 14:54:31: CostInitialize. Return value 1.
Action 14:54:31: FileCost. Computing space requirements
Action start 14:54:31: FileCost.
Action ended 14:54:31: FileCost. Return value 1.
Action 14:54:31: IsolateComponents.
Action start 14:54:31: IsolateComponents.
Action ended 14:54:31: IsolateComponents. Return value 0.
Action 14:54:31: CostFinalize. Computing space requirements
Action start 14:54:31: CostFinalize.
Action ended 14:54:31: CostFinalize. Return value 1.
Action 14:54:31: RSSPTarget.28B19132_4741_4761_840F_AC515130EC08.
Action start 14:54:31: RSSPTarget.28B19132_4741_4761_840F_AC515130EC08.
Action ended 14:54:31: RSSPTarget.28B19132_4741_4761_840F_AC515130EC08. Return value 1.
Action 14:54:31: RSSP_CAStreamBinary.28B19132_4741_4761_840F_AC515130EC08.
Action start 14:54:31: RSSP_CAStreamBinary.28B19132_4741_4761_840F_AC515130EC08.
Action ended 14:54:33: RSSP_CAStreamBinary.28B19132_4741_4761_840F_AC515130EC08. Return value 1.
Action 14:54:33: SqlFollowComponentsValidate.BB9BCD10_C507_4374_A5FC_3F04C705A420. Examining SxS Components
Action start 14:54:33: SqlFollowComponentsValidate.BB9BCD10_C507_4374_A5FC_3F04C705A420.
<Func Name='LaunchFunction'>
Function=SqlFollowComponentsValidate
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: SqlFollowComponentsValidate
PerfTime Start: SqlFollowComponentsValidate : Mon Jan 22 14:54:35 2007
<Func Name='SqlFollowComponentsValidate'>
PerfTime Stop: SqlFollowComponentsValidate : Mon Jan 22 14:54:35 2007
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
Action ended 14:54:35: SqlFollowComponentsValidate.BB9BCD10_C507_4374_A5FC_3F04C705A420. Return value 1.
Action 14:54:35: IsDotNet20Installed.
Action start 14:54:35: IsDotNet20Installed.
Feature SharepointRS install action does not match 2.
Not all features are being removed.
One or more .NET Framework assemblies found in MsiAssembly table require the GAC, need to check for the .NET Framework
Action ended 14:54:35: IsDotNet20Installed. Return value 1.
Action 14:54:35: CA_SetARPINSTALLLOCATION.
Action start 14:54:35: CA_SetARPINSTALLLOCATION.
Action ended 14:54:35: CA_SetARPINSTALLLOCATION. Return value 1.
Action 14:54:35: SetODBCFolders. Initializing ODBC directories
Action start 14:54:35: SetODBCFolders.
Action ended 14:54:35: SetODBCFolders. Return value 0.
Action 14:54:35: MigrateFeatureStates. Migrating feature states from related applications
Action start 14:54:35: MigrateFeatureStates.
Action ended 14:54:35: MigrateFeatureStates. Return value 0.
Action 14:54:35: InstallValidate. Validating install
Action start 14:54:35: InstallValidate.
Action ended 14:54:35: InstallValidate. Return value 1.
Action 14:54:35: InstallInitialize.
Action start 14:54:35: InstallInitialize.
Action ended 14:54:36: InstallInitialize. Return value 1.
Action 14:54:36: AllocateRegistrySpace. Allocating registry space
Action start 14:54:36: AllocateRegistrySpace.
Action ended 14:54:36: AllocateRegistrySpace. Return value 1.
Action 14:54:36: ProcessComponents. Updating component registration
Action start 14:54:36: ProcessComponents.
Action 14:54:36: GenerateScript. Generating script operations for action:
GenerateScript: Updating component registration
Action ended 14:54:36: ProcessComponents. Return value 1.
Action 14:54:36: UnpublishComponents. Unpublishing Qualified Components
Action start 14:54:36: UnpublishComponents.
Action ended 14:54:36: UnpublishComponents. Return value 1.
Action 14:54:36: MsiUnpublishAssemblies. Unpublishing assembly information
Action start 14:54:36: MsiUnpublishAssemblies.
Action ended 14:54:36: MsiUnpublishAssemblies. Return value 1.
Action 14:54:36: UnpublishFeatures. Unpublishing Product Features
Action start 14:54:36: UnpublishFeatures.
Action ended 14:54:36: UnpublishFeatures. Return value 1.
Action 14:54:36: StopServices. Stopping services
Action start 14:54:36: StopServices.
Action ended 14:54:36: StopServices. Return value 1.
Action 14:54:36: DeleteServices. Deleting services
Action start 14:54:36: DeleteServices.
Action ended 14:54:36: DeleteServices. Return value 1.
Action 14:54:36: UnregisterComPlus. Unregistering COM+ Applications and Components
Action start 14:54:36: UnregisterComPlus.
Action ended 14:54:36: UnregisterComPlus. Return value 0.
Action 14:54:36: SelfUnregModules. Unregistering modules
Action start 14:54:36: SelfUnregModules.
Action ended 14:54:36: SelfUnregModules. Return value 1.
Action 14:54:36: UnregisterTypeLibraries. Unregistering type libraries
Action start 14:54:36: UnregisterTypeLibraries.
Action ended 14:54:36: UnregisterTypeLibraries. Return value 1.
Action 14:54:36: UnregisterFonts. Unregistering fonts
Action start 14:54:36: UnregisterFonts.
Action ended 14:54:36: UnregisterFonts. Return value 1.
Action 14:54:36: RemoveRegistryValues. Removing system registry values
Action start 14:54:36: RemoveRegistryValues.
Action ended 14:54:36: RemoveRegistryValues. Return value 1.
Action 14:54:36: UnregisterClassInfo. Unregister Class servers
Action start 14:54:36: UnregisterClassInfo.
Action ended 14:54:36: UnregisterClassInfo. Return value 1.
Action 14:54:36: UnregisterExtensionInfo. Unregistering extension servers
Action start 14:54:36: UnregisterExtensionInfo.
Action ended 14:54:36: UnregisterExtensionInfo. Return value 1.
Action 14:54:36: UnregisterProgIdInfo. Unregistering program identifiers
Action start 14:54:36: UnregisterProgIdInfo.
Action ended 14:54:36: UnregisterProgIdInfo. Return value 0.
Action 14:54:36: UnregisterMIMEInfo. Unregistering MIME info
Action start 14:54:36: UnregisterMIMEInfo.
Action ended 14:54:36: UnregisterMIMEInfo. Return value 0.
Action 14:54:36: RemoveIniValues. Removing INI files entries
Action start 14:54:36: RemoveIniValues.
Action ended 14:54:36: RemoveIniValues. Return value 1.
Action 14:54:36: RemoveShortcuts. Removing shortcuts
Action start 14:54:36: RemoveShortcuts.
Action ended 14:54:36: RemoveShortcuts. Return value 0.
Action 14:54:36: RemoveEnvironmentStrings. Updating environment strings
Action start 14:54:36: RemoveEnvironmentStrings.
Action ended 14:54:36: RemoveEnvironmentStrings. Return value 1.
Action 14:54:36: RemoveDuplicateFiles. Removing duplicated files
Action start 14:54:36: RemoveDuplicateFiles.
Action ended 14:54:36: RemoveDuplicateFiles. Return value 1.
Action 14:54:36: RemoveFiles. Removing files
Action start 14:54:36: RemoveFiles.
Action ended 14:54:36: RemoveFiles. Return value 0.
Action 14:54:36: RemoveFolders. Removing folders
Action start 14:54:36: RemoveFolders.
Action ended 14:54:36: RemoveFolders. Return value 0.
Action 14:54:36: CreateFolders. Creating folders
Action start 14:54:36: CreateFolders.
Action ended 14:54:36: CreateFolders. Return value 0.
Action 14:54:36: MoveFiles. Moving files
Action start 14:54:36: MoveFiles.
Action ended 14:54:36: MoveFiles. Return value 1.
Action 14:54:36: InstallFiles. Copying new files
Action start 14:54:36: InstallFiles.
InstallFiles: File: Copying new files, Directory: , Size:
Action ended 14:54:36: InstallFiles. Return value 1.
Action 14:54:36: DuplicateFiles. Creating duplicate files
Action start 14:54:36: DuplicateFiles.
Action ended 14:54:36: DuplicateFiles. Return value 1.
Action 14:54:36: PatchFiles. Patching files
Action start 14:54:36: PatchFiles.
Action ended 14:54:36: PatchFiles. Return value 0.
Action 14:54:36: BindImage. Binding executables
Action start 14:54:36: BindImage.
Action ended 14:54:36: BindImage. Return value 1.
Action 14:54:36: RegisterClassInfo. Registering Class servers
Action start 14:54:36: RegisterClassInfo.
Action ended 14:54:36: RegisterClassInfo. Return value 1.
Action 14:54:36: RegisterExtensionInfo. Registering extension servers
Action start 14:54:36: RegisterExtensionInfo.
Action ended 14:54:36: RegisterExtensionInfo. Return value 1.
Action 14:54:36: RegisterProgIdInfo. Registering program identifiers
Action start 14:54:36: RegisterProgIdInfo.
Action ended 14:54:36: RegisterProgIdInfo. Return value 0.
Action 14:54:36: RegisterMIMEInfo. Registering MIME info
Action start 14:54:36: RegisterMIMEInfo.
Action ended 14:54:36: RegisterMIMEInfo. Return value 0.
Action 14:54:36: Write_sqlLocalServers.BB9BCD10_C507_4374_A5FC_3F04C705A420. Registering local servers
Action start 14:54:36: Write_sqlLocalServers.BB9BCD10_C507_4374_A5FC_3F04C705A420.
<Func Name='LaunchFunction'>
Function=Write_sqlLocalServers
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlLocalServers
PerfTime Start: Write_sqlLocalServers : Mon Jan 22 14:54:36 2007
<Func Name='Write_sqlLocalServers'>
PerfTime Stop: Write_sqlLocalServers : Mon Jan 22 14:54:36 2007
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
Action ended 14:54:36: Write_sqlLocalServers.BB9BCD10_C507_4374_A5FC_3F04C705A420. Return value 1.
Action 14:54:36: WriteRegistryValues. Writing system registry values
Action start 14:54:36: WriteRegistryValues.
WriteRegistryValues: Key: Writing system registry values, Name: , Value:
Action ended 14:54:36: WriteRegistryValues. Return value 1.
Action 14:54:36: Write_sqlVerIndependentProgID.BB9BCD10_C507_4374_A5FC_3F04C705A420. Restoring COM Servers
Action start 14:54:36: Write_sqlVerIndependentProgID.BB9BCD10_C507_4374_A5FC_3F04C705A420.
<Func Name='LaunchFunction'>
Function=Write_sqlVerIndependentProgID
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlVerIndependentProgID
PerfTime Start: Write_sqlVerIndependentProgID : Mon Jan 22 14:54:37 2007
<Func Name='Write_sqlVerIndependentProgID'>
PerfTime Stop: Write_sqlVerIndependentProgID : Mon Jan 22 14:54:37 2007
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
Action ended 14:54:37: Write_sqlVerIndependentProgID.BB9BCD10_C507_4374_A5FC_3F04C705A420. Return value 1.
Action 14:54:37: WriteIniValues. Writing INI files values
Action start 14:54:37: WriteIniValues.
Action ended 14:54:37: WriteIniValues. Return value 1.
Action 14:54:37: WriteEnvironmentStrings. Updating environment strings
Action start 14:54:37: WriteEnvironmentStrings.
Action ended 14:54:37: WriteEnvironmentStrings. Return value 1.
Action 14:54:37: RegisterFonts. Registering fonts
Action start 14:54:37: RegisterFonts.
Action ended 14:54:37: RegisterFonts. Return value 1.
Action 14:54:37: RegisterTypeLibraries. Registering type libraries
Action start 14:54:37: RegisterTypeLibraries.
Action ended 14:54:37: RegisterTypeLibraries. Return value 1.
Action 14:54:37: SelfRegModules. Registering modules
Action start 14:54:37: SelfRegModules.
Action ended 14:54:37: SelfRegModules. Return value 1.
Action 14:54:37: RegisterComPlus. Registering COM+ Applications and Components
Action start 14:54:37: RegisterComPlus.
Action ended 14:54:37: RegisterComPlus. Return value 0.
Action 14:54:37: InstallServices. Installing new services
Action start 14:54:37: InstallServices.
Action ended 14:54:37: InstallServices. Return value 1.
Action 14:54:37: StartServices. Starting services
Action start 14:54:37: StartServices.
Action ended 14:54:37: StartServices. Return value 1.
Action 14:54:37: RegisterUser. Registering user
Action start 14:54:37: RegisterUser.
RegisterUser: Registering user
Action ended 14:54:37: RegisterUser. Return value 1.
Action 14:54:37: RegisterProduct. Registering product
Action start 14:54:37: RegisterProduct.
RegisterProduct: Registering product
Action ended 14:54:37: RegisterProduct. Return value 1.
Action 14:54:37: PublishComponents. Publishing Qualified Components
Action start 14:54:37: PublishComponents.
Action ended 14:54:37: PublishComponents. Return value 1.
Action 14:54:37: MsiPublishAssemblies. Publishing assembly information
Action start 14:54:37: MsiPublishAssemblies.
MsiPublishAssemblies: Application Context:Publishing assembly information, Assembly Name:
Action ended 14:54:41: MsiPublishAssemblies. Return value 1.
Action 14:54:41: PublishFeatures. Publishing Product Features
Action start 14:54:41: PublishFeatures.
PublishFeatures: Feature: Publishing Product Features
Action ended 14:54:41: PublishFeatures. Return value 1.
Action 14:54:41: PublishProduct. Publishing product information
Action start 14:54:41: PublishProduct.
1: Publishing product information
Action ended 14:54:41: PublishProduct. Return value 1.
Action 14:54:41: CreateShortcuts. Creating shortcuts
Action start 14:54:41: CreateShortcuts.
Action ended 14:54:41: CreateShortcuts. Return value 0.
Action 14:54:41: RSSP_CAInstall.28B19132_4741_4761_840F_AC515130EC08.
Action start 14:54:41: RSSP_CAInstall.28B19132_4741_4761_840F_AC515130EC08.
RSSP_CAInstall.28B19132_4741_4761_840F_AC515130EC08:
Action ended 14:54:41: RSSP_CAInstall.28B19132_4741_4761_840F_AC515130EC08. Return value 1.
Action 14:54:41: InstallFinalize.
Action start 14:54:41: InstallFinalize.
Action 14:54:41: ProcessComponents. Updating component registration
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {CBAF955A-055A-41DC-B15D-6260306131EF} 3: 02:SOFTWAREMicrosoftMicrosoft SQL Server 2005SharePointRSCurrentVersionVersion
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {DF5E1775-8C5A-4BF1-AFFA-EF850CA62107} 3: 02:SOFTWAREMicrosoftMicrosoft SQL Server 2005SharePointRSSharePointRSMSIRefCountUninstall
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {4A7964EA-EA8E-4449-A1CF-3763C601EFE7} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportService2006.asmx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {38FC1196-9640-416E-A529-E4BB081274E0} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportExecution2005.asmx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {68D6680B-20A1-4719-A9A3-6975C3900413} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportServiceAuthentication.asmx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {F2878C69-3635-4E6C-BD69-83D443DC58D4} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportExecution2005wsdl.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {966335E6-36F8-418A-956E-915D3FC16E7D} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportService2006wsdl.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {B06B188B-8B4E-4F66-9ECA-5D0ED3AC6F67} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportExecution2005disco.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {E2DF6CAA-2AF6-4D7F-9E43-283E28246FFF} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportService2006disco.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {CD0EDB40-71D7-43E0-8976-304A58FF3F7A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportServiceAuthenticationdisco.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {72C412F7-E618-4BDA-8A99-B1C8660B2F38} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportServerReportServiceAuthenticationwsdl.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {E62A4631-F371-4096-A802-B166C0201495} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderReportbuilder.application
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {541E2FDC-A9B3-49BE-A4D8-7129FFDDC3FD} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderReportbuilder.exe.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {CFC35852-2016-45B7-AF10-F0D843A0FDAB} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderReportbuilder.exe.manifest
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {CD518770-E3A0-4CB1-A0A3-E10FBEE4E99A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderReportbuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {7CB37147-DCCE-4A9F-B088-FA8C070A1634} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="x86",Culture="neutral"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {236A9934-68AD-435E-B128-8E636BE32975} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="x86",Culture="neutral"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C1241026-21AE-43E1-9401-5070569392C2} 3: <Microsoft.ReportingServices.SharePoint.Common,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="x86",Culture="neutral"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {1290D795-1909-49E1-B9DE-B983E60A41BC} 3: <RSSharePointSoapProxy,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="x86",Culture="neutral"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {B7E42968-3DB9-4758-846D-0EB577F9BC8A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12CONFIGWebconfig.rs.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {985B87FD-D2F4-4FD4-87B6-848C68AED4F1} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12CONFIGResourcesReportServer.EN.resx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {78322079-38ED-4F81-A839-13766017A7C4} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESReportServerFeature.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {86AB62E0-A54B-4BBC-A990-0BE56C0D02F4} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESReportServerWebPartsElements.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {E2045507-FF11-4348-9406-270C4743A7E9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESReportServerReportServerContentTypes.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C72D6866-DB3F-45B5-A357-F90B4A211EEB} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESReportServerAdminUIAdminUIEntryPoints.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {29528823-535A-4535-83DB-E51D859BC700} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESReportServerItemCustomACtionsecbExtension.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {AC9A3582-D31A-486D-B6F7-D017D668B428} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESReportServerResourcesResources.resx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {1C9A3582-231A-386D-46F7-5017D668B428} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESReportServerEULALicense_RSSharePoint_EN.txt
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {CDBB0396-A3FF-437A-ABBE-3E3E551CB057} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEFEATURESReportServerReportViewer.dwp
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6756F84F-A77A-40E8-A8DE-EFFBEBE7D812} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerdatasource.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {FA68495C-CFA4-4896-9249-D476D0996935} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServer16doc_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {058F4F29-2643-4DAE-9183-F93219216BF9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServer16model_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C2F7B33A-7DC2-4BEC-A6EB-DE7624E71B5C} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerLine_err1_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {0F112DF8-45AB-4864-A2F6-4798CC9CAFA2} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerDELITEM_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {D033D3B7-E35E-4AC8-8A7F-BC9D8768C98A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerNewSnapshot_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C33A8382-18EB-46C5-A558-EB70BA3904B4} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServer16newsubscription_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {A2A66BAE-A5ED-4BAF-81EC-FBA0DE57E7B7} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerup.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {380AC2B1-3138-47A6-897F-A20E7D0D2C70} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerupdisabled.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {385DEFF5-41E2-4377-A460-818120FF78BB} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServeranner.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {7528F783-8849-463F-89E1-8B71CA3CDA6C} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServermodel_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {8293A50D-30EA-47A8-B4E9-BEB789EB794E} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerentity_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {FE61C796-2722-47C1-9D8D-066F6FF511F6} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerfield_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {DA0FAEDE-A426-4066-8C96-37678C75BA6B} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServermodelfolder_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {A8FB4729-8F36-4A18-9FE5-89524A26E4F6} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServeritempickerdialog.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {7B1B3236-5F41-415B-8CBE-2EEBB14AF0C0} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServer
eportwebpart.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {E0795E62-3C20-447F-A0A2-40D0EBE86BE3} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerewschedule_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {60B72CD4-87D8-4283-BCF3-76E0730D1D6D} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServerpause_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C9F2C29E-00AE-4255-89B2-EC86CB6B55A1} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServer
esume_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {69EA3FBF-6830-4E96-AA4C-B6A0B0A2F6CB} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServermanage_subscription.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6D30A6F6-FCF6-4FED-8E28-BA2A738FE44C} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServereditreport.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {8AE784D4-40E6-4EBA-8C92-AE233855F27C} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServericongo01.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {3F390C3C-E6B0-433F-B2F5-89F160C8CDF1} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImagesReportServericongo02.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {D99F9779-D11D-43BD-B3F7-CCFEA5D30E10} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImageslg_ReportServerewreport_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {F0916C48-86A5-40ED-B473-F5A897DABCC1} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImageslg_ReportServerdatasource.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {D59A2BDC-AD96-4963-864F-DD1BEF951308} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEImageslg_ReportServer16model_sp.gif
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {4A506FE9-BB62-47EA-8DFE-E036C3F0B775} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSLayouts.sitemap.rs.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {027057EA-28ED-420E-BB2F-EB213AA6F976} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerDataSourceList.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {375293B2-3512-451D-805D-46F9F5B22088} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerDataSourceProperties.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {F56A63E0-C24E-45A5-87E4-A18F5DC2D932} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerDependentItems.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {BED5CA60-F997-45DB-8A98-46F3CBCF4ACD} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerManageSubscriptions.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6F12D780-7A74-498A-AAEF-EDF089728766} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerManageTrustedAccounts.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {0C3E4A4E-19BF-427D-B405-05E91F6766FE} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerReportServerSiteSettings.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {986283FC-2638-48C1-846E-6436390D918B} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerRSAction.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C16ACE21-61DF-488A-B3FF-99C5F22A4C1C} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerRSViewerPage.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {59417DA0-0891-44EA-847C-72762FA05FD9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerParameterList.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {FB44D7C6-2E1A-42B4-9CDF-8C40CDAA3C5F} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerParameterProperties.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {1C5DA965-E7A5-4DA6-8458-4869487C27A3} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerReportHistory.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {1A1FF5AE-81EF-4F30-9EFF-00EF5C9275AE} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerSharedDataSource.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {968D3022-8E20-48F0-88AD-999392C61DDA} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerSPSubscriptionProperties.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {2B6DA776-FC30-472C-9FD7-AC4E3D2CC39D} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerModelClickThrough.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {5075ACB5-8759-4560-A120-AEB23E272F54} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerModelItemSecurity.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {42689258-E5DD-48B1-ABE9-6493E0502771} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerReportExecution.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {ADCD5587-53DE-438D-A2A7-05CB77D6FBCC} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerRSItemPicker.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {DC342F57-E0D0-4800-BCCE-B4FE8CA5BC9B} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerScheduleList.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {39A99769-5AD5-4CBC-A9E4-6135C3DDCB45} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerScheduleProperties.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {13506FE9-1B6C-47EA-8DFE-E236C3F4B775} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerUserCredentials.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {AEB1CE55-0F9D-4D20-A320-51A03ADD7353} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerGenerateModel.aspx
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {3B4FC636-835F-4C6F-8076-D4A180BC4F6E} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATELAYOUTSReportServerStylesSqlrvdefault.css
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C83E6A28-E469-43AC-82C0-0EDA377ABF23} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1028MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {817D59B4-E0F6-42A0-93AD-6DFE18B2BB0E} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1028
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {2A53E763-5312-4D47-9245-A860FA0F56E4} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1029MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {9B1AD183-5D56-48BC-9D54-4B79E8EA44A7} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1029
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {EA60D556-3E7A-455B-A13F-7E11D721C4DE} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1030MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {0273F9D3-4076-4597-A6F9-6C828BBDD7A7} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1030
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {44E0E62F-6920-46F6-98A2-5E94DACFCED2} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1031MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {554FBB3C-D42B-4497-98F6-781400903431} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1031
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {48218D83-E66E-4185-B2C7-57929EE26F9D} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1032MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {0DF1FD2D-674B-492B-9F18-7CD8AB6334DE} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1032
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {A43A3BED-94A2-455A-B3DE-0AD0EF679B89} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1033MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {0606DF87-CF50-414C-AFF4-481A83FC9DF5} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1033
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {2BA9356E-EAF2-4CF4-B8C2-1E0E456A3BCA} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1035MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {48109584-A722-4697-A7C4-547C8B75A9F5} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1035
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {BB3F8C1C-727A-4082-8C70-9EA892B5EBA3} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1036MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {5F87085C-15AD-45DE-A79A-B853989A6130} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1036
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {F71715F4-E30B-46C3-AB84-F03A02D117A0} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1038MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6114B047-BF4F-44FD-A7C0-4B1DEFE66B9B} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1038
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {68FE27C2-1AB5-435A-BFA5-13071D3F4145} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1040MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C36E478D-9214-479F-8673-63C930D9A07C} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1040
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C42A376B-7B26-444D-B8E5-30787F2CC826} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1041MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {BEB30F8A-C587-4DA6-85F3-05E913A1376E} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1041
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {2C1E1DBA-B40E-484E-809E-A50E1F8D133A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1042MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {A4A4BFFD-1F7B-444D-A57F-FF6AB1DA4FEE} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1042
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {870838F7-6EEF-4B61-A157-597DE8AF85E6} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1043MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {48113685-8D20-4288-B8C8-388CB40F1919} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1043
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {8CAE52CA-2551-4039-B747-1AB579F614D9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1044MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {E68C0517-105B-4346-A62E-5A7C318A91A9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1044
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {4306901A-89F9-4191-B7A7-284038B9DCF6} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1045MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {F16777B1-620F-4818-8778-3E89B423073E} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1045
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6FF73A55-E40D-4C1A-A8AB-FBF021759552} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1046MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {4DCF4659-DC03-4852-814A-20DE986A4CB9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1046
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {19C0EC0E-EA3D-42F6-9BA9-478DD4A5B525} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1049MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {4766B4F4-D6BA-417A-98D9-0317DC26FFED} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1049
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {B336DF5C-0656-4349-8EB7-020331C520D9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1053MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {545600FD-B80D-4ABF-8B0C-CD449D7E2E83} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1053
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {1787055D-61D4-45EC-8880-57EC5BC68E99} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1055MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6E21117F-00FE-4D98-989A-82EE0EF66915} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab1055
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {179F8097-0CD6-490F-AE28-353C97E5DAE6} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab2052MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {9E34C562-C845-4E86-B9EB-54A2A82C9560} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab2052
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C0858C03-0701-41A4-9630-C76DA1396662} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab2070MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {9E4651F7-30A2-44EF-AFF5-CAAB2F8FF009} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab2070
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {A8539AF8-C7D5-45F4-A758-3B30D14440B5} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab3082MS.WSS.RS.HC.cab
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {22C246B9-CCB2-4340-A700-8636B37ACF1D} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12HCCab3082
eadme_rsaddin.htm
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {D7C6417F-8AAC-4EDA-9EA7-72E883E98D2C} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEXMLServerFiles_ReportServer.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {E0FDD894-58E1-4D92-82B0-E7C1A465EF90} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12TEMPLATEXMLHELPReportingServices.xml
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {AC72B4A3-6D73-4342-90CA-CFFED78FA416} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderzh-CHTReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {5754FECE-04E1-4D94-8088-DBF36DC4E6CB} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1028ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {782CDAF9-A243-4417-9C4B-F0FB79AE1C86} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuildercsReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {D7530D08-CB26-433A-920B-7B4CF3AFF25A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1029ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {8CB2AF0B-9F27-4000-A027-9A84C6B410C1} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderdaReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {CA415100-9D1B-427D-BA15-789AEC828B75} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1030ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {39CF1800-74E7-4A08-8959-FE44958A96AB} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderdeReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {B9BC5656-13D6-4884-80B1-FD1A077A01A9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1031ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {4DA4CFFD-86E6-47F8-BD89-AA0848D1ECE2} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderelReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {7748D29E-B8A4-469B-AA3C-33811BF0A4A9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1032ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {7FB13D5B-395B-4237-9E60-FC18555D5E30} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderfiReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {59AB8FCF-16C0-417B-88E9-203AFF733F32} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1035ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {852CCDED-0610-493D-B9C9-476027B3C308} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderfrReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {1948BD88-F21B-46C1-A407-FBCA4D9062F3} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1036ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {CC091952-4547-4FAC-BD15-16669CFEF3D3} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderhuReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {A2D7E68C-1C0D-4F51-BD67-0251DB33214E} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1038ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {B4F21AA7-4FBB-4F3C-94D8-E8396A88CA4D} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderitReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {03EE29C4-65EB-46F2-B4D9-C8B1C63AC972} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1040ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {42B61BFB-5EBF-42CA-AD7D-2FF5F0423C00} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderjaReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {741DB6D7-9E20-41BC-B0CC-BEDEAC3E28C0} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1041ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {FC2409E0-9A09-4431-9B65-9263F051D059} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderkoReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {DE82BF9E-07A7-4AE9-A802-4293E917CD7F} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1042ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {0286ABCF-A73C-47C1-9990-AFD1E0934F9A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderlReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {FD998749-D357-4031-AE60-C83B3B1C3381} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1043ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {1DC67D6A-6A8F-44AC-8AC2-127BF3B5B0BF} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderoReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {05F390EE-FEF2-40B5-8178-442862E7F9DE} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1044ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {3ED9B172-5BC4-41E1-81B9-FC8F47B5643D} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderplReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6280D684-28D9-424C-AC0B-2B6B7A82D4AA} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1045ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6FC319FA-9270-443C-A8A2-D812FE287C01} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderptReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {88679107-95F4-4D6E-831A-22123E811FA2} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1046ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {456C7C87-6AA2-440B-AE84-23BFF924DE86} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder
uReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {F74DE1E7-B53C-436B-B483-8B95138848FF} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1049ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {78FBC369-1CF4-43AD-993F-C13DB57CB9DC} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuildersvReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {69B16353-FF2C-4378-95C4-EE3F4CE00B92} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1053ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {B666075F-206C-44B8-B68A-EA5D4380BEB9} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder rReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {05F3A36B-7252-4503-8BB4-FAAB1CAB28D1} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder1055ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {884D547A-43ED-4385-AC78-69F829F66B8A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderzh-CHSReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {9A392E13-7798-47B7-98E9-D996DEC351F7} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder2052ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {038BD6E9-70A7-4735-B0C9-DF65CBDBB7DD} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderpt-PTReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {49AE6E8D-EC57-4D5D-A70E-B7083BEC5CE3} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder2070ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {3104CED8-D831-440F-A4E3-324326094FB2} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilderesReportBuilder.resources.dll.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {29226DFA-A53D-405F-9FB4-AA3A562DF34A} 3: C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12ISAPIReportBuilder3082ReportBuilder.chm.deploy
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {14A96A0E-D1F9-4B0E-B9D5-6F5E5FBE9206} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="zh-CHT"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {B7493AF3-AB77-4092-BD2D-CD601DACF0EA} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="zh-CHT"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {279720A1-2ABE-418B-826B-017F0787434D} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="zh-CHT"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {F3BAD61C-446A-49A8-BAF6-23AF2F1B85F8} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="zh-CHT"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {8D9656BF-5652-40DB-89FB-7FE7BF026EAB} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="cs"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {C10EA131-4B81-4551-A4C5-5B8A74E187D2} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="cs"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {0A7AAED1-762E-4240-AB42-64DD30644DF1} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="cs"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {690D3450-601B-49B3-8718-C31AA1393851} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="cs"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {562869E3-F5F3-40F6-8278-DDC89184DC7C} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="da"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {28DF9830-60B7-475A-B9D4-3D80265BDAF7} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="da"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {41736099-F8C6-4B8F-A10C-6C9F56EF5BDC} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="da"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {73F1BD5C-EC49-4FD1-A0E7-62B6D893C221} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="da"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {94827AA2-2198-448B-BD8D-1AAD8A82B5BD} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="de"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {B53210CD-D5C2-4F08-9012-3F7A53065106} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="de"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {5A120F59-1AF5-479E-A4D6-50EF7A0BEDB4} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="de"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {85791D2F-A849-4646-9C6E-A5944446D2EF} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="de"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {1D50AE0A-9F3F-407B-AAAF-E0787C32BB64} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="el"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {69A658EF-B89D-4F35-9FE4-2E5700C68D8C} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="el"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {69D9A355-EA74-43F1-A2FF-2E2A610C9F84} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="el"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {EC8060F2-60CE-486F-B039-78F86D5213B5} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="el"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {D05201BA-6BF3-47C4-95D9-D34E4F230481} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="fi"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {81AFF03A-4AE4-460A-B428-F47CFEA45DE2} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="fi"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {CCF95D6B-78EF-4088-B372-C9E424F5ED35} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="fi"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {129D95E8-24A7-4D43-BF53-AC3BB78B337F} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="fi"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {647DDBB6-E929-4CDB-A9A7-8249B0B324D8} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="fr"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {9F98BC04-75D3-4346-B31F-C80FF482F5B8} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="fr"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {4535580E-8359-4FEB-87E3-B168CB7FA993} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="fr"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {70720C31-89E9-4536-84E6-9C0F8C430C7F} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="fr"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {A0668C3C-943A-4B3A-85CD-B327457E7478} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="hu"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {3DD90913-5F58-417A-ADCE-CC708D46AB8C} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="hu"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {523ECFB4-03BE-4EBF-8E8B-492631926B73} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="hu"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {DB9E308A-5CEF-43F8-B8EE-7E5FC6CD255E} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="hu"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {A3910145-431F-4C7C-A85F-9393336FFA3D} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="it"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {99A59CC6-0DA6-498E-9A56-83F4D64CD884} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="it"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {26B7661B-05C9-42C3-803D-DC38B93ED23D} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="it"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {036E03DD-AED7-46E4-B1C0-3D242BACC3D2} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="it"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {6B214FF6-39E4-4D62-A516-D11A23E7606A} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="ja"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {351690B3-2469-42F2-A067-796FF47E3656} 3: <Microsoft.ReportingServices.SharePoint.UI.WebParts.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="ja"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {E3429180-7641-4BA8-BDB6-4D10449D7654} 3: <Microsoft.ReportingServices.SharePoint.Common.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="ja"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {D341CBCC-4D57-4D8D-ADE1-F4296B301D59} 3: <RSSharePointSoapProxy.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="ja"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {60B530F6-C6B1-4A70-B023-6952EF0FAACD} 3: <Microsoft.ReportingServices.SharePoint.UI.ServerPages.resources,Version="9.0.242.0",FileVersion="9.0.3033.0",PublicKeyToken="89845dcd8080cc91",processorArchitecture="MSIL",Culture="ko"
1: {5EF42CA5-A460-49AD-A6C1-C996088C99A5} 2: {FF95A789-549C-45F8-BB35-03C2785BB712} 3: &l

View 10 Replies View Related

Sharepoint 2007 Report Services Addin Install Problem

Jan 12, 2007

I have the following setup:

Windows 2003, Sahrepoint 2007, Report Services Addin (v9.00.3033) on one machine

Windows 2003, SQL Server 2005 SP2 CTP (v9.00.3033) on another.

When I install the Report Service addin on the Sharepoint machine, the install goes fine; however, when I go to the Application Management screen in Sharepoint Central Admin I don't see a "Reporting Services" section or a "Manage integration settings" link.

Any thoguths?

Thanks,

Atul

View 12 Replies View Related

NameSpace Of ReportingService Class

Nov 29, 2005

I can't find the ReportingService's namespace... i see ReportingService inerhits from System.Web.Services.Protocols.SoapHttpClientProtoco but any code what i found its impossible to compile, i need the namespace...

View 3 Replies View Related

Specifying Language For ReportingService Render Method

Oct 3, 2007

I have a report that I'm hosting on SSRS. I have it setup for localization so if someone hits the report directly and their default language setting in their browser is ja-JP the report will display in Japanese. I am using the User!Language variable for this.

I am primarily displaying this report through an ASP.NET app however and am calling the Render method on the ReportingService service, then displaying the returned HTML in a literal control. This works great except, obviously, with this proxy type of set up the user's browser settings get lost in the shuffle. I can retrieve the browser settings easily enough in my ASP.NET application but how do I pass those settings along to SSRS? I have tried setting the CurrentCulture and CurrentUICulture on the thread executing the request but it still comes back in English. I have also tried setting the Language property (as shown below) but it seems as though that would change the Language on the report for everyone, not just my session.


Property[] props = new Property[1];


props[0] = new Property();

props[0].Name = "Language";

props[0].Value = "ja-JP";

report.SetProperties(reportPath, props);

Can someone help?

Thanks

View 1 Replies View Related

ReportingService.CreateSubscription Sample Code

Apr 18, 2008



Hi,

If somebody have worked on providing the code for the selection of delivery method and delivery schedule page in aspx . Then please share it with me. I am working on creating a Subscription page using aspx rather then reporting services page.

Please let me know if there are any controls provided by reporting services or some 3rd party for this.

Thanks & Regards,

Sam

View 3 Replies View Related

Reporting Services And Sharepoint Integration - Sharepoint Alternate Access Mappings (Zones)

Mar 2, 2007

I get the following error when I try to navigate to a report/model/data source, stored in a Sharepoint Document Library using a Sharepoint URL based on an Extranet or Intranet zone - but it works OK using the url for the Default zone:

System.Web.Services.Protocols.SoapException: The specified path refers to a SharePoint zone that is not supported. The default zone path must be used. ---> Microsoft.ReportingServices.Diagnostics.Utilities.SecurityZoneNotSupportedException: The specified path refers to a SharePoint zone that is not supported. The default zone path must be used.


Is this a limitation of the SQLRS-WSS3 integration or is there a workaround?

Many thanks to anyone who can help!





View 22 Replies View Related

Excel Time-Series Addin Problem

Jun 22, 2006

Have an Excel Spreadsheet with two columns and 52 rows (retail sales)

Date Qty

1 5

2 8



etc



Tried to run the above Addin. Error message:

"Session mining object (...) can not be created on this instance."



Any ideas?



Thanks,

Sergei.

View 1 Replies View Related

Remote Connecting To MSSQL Through A VSTO Addin

Jan 28, 2008



Hi there everybody

I am a novice in using MSSQL and Windows 2003 solutions so I am having some problems.

I have made an excel addon in VSTO that connects to a MSSQL2005 server running on Windows 2003 on our internal domain, and it works great. Connection when I specify the domain adress is flawless. The thought is though that the addin is supposed to been used also outside our domain, so I have opened up our router and redirects all traffic to and from port 1433 to our MSSQL-server. This part should be ok.


I can then not connect to this server with our external ip specified. The error message Visual Studio produces is "An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 -A connection attempt failed because the connected party did not properly respond after a period of time, or established connecteion failed because connected host has failed to respond.)"


I have read around and tried to fix this myself. I've specified to accept "Locale and remote connections" in the Surface Area Configuration Tool that shipped with MSSQL on both TCP/IP and named pipes. In the SQL Server Configuration Manager is the protocols Shared Memory and TCP/IP enabled. I have enabled all the IP-adresses under TCP/IP and specified 1433 as the port to use for all of them.


As for possible other problems I can see:
I have read a couple of places that people have tried to connect with the MSSQL server through telnet when specifying the port 1433 (telnet mydomain.net 1433). I have tried this but telnet is not getting a connection. Dont I have to open/forward more ports on the router to get telnet through?

I cant ping our external ip. Isnt this also a problem that is related to that I have not opened/forwarded ports on the router to our MSSQL server?


Do anyone of you have any tips or steps to take to narrow the problem down? This is not the forum for VSTO but thats not really where the problem is either, I think. It is probably somewhere in the configuration of MSSQL or Windows 2003. The server machine is set up as domain controller and DNS server for our local net.


I will appreciate all input, I am stuck at the moment...

Stein Agnar Sannes
Programmer (c, php, perl, java)

View 1 Replies View Related

Sharepoint Integration Microsoft.ReportingServices.SharePoint.UI.WebParts.dll

Feb 2, 2007

Does anyone know the location of Microsoft.ReportingServices.SharePoint.UI.WebParts.dll after you install the web part? I am wondering if I can inherit from this web part to wrap some other functionality into it. I know that i see it in the GAC buyt can't seem to find it so I can look at the assembly using reflector.

Also, how easy is it to pass in parameters to the Report Viewer?

Thanks!

Erik



View 6 Replies View Related

Problems With SharePoint Integration And Reporting On SharePoint With SSRS

Jan 17, 2008

Since I wasn't getting any replies with answers or suggestions to my initial posting, I figured I would continue to list the problems and solutions I've encountered while trying to setup and utilize SharePoint integration mode, and read data from SharePoint with SSRS reports (developed in VS2005). Hopefully this is helpful to anyone that is also trying to learn all this stuff and figure it out.

(Single server - W2K3R2_SP2 as: DC / SQL2005 Standard / MOSS2007 Enterprise - see the bottom of this posting for the steps I took to set that up)

Note: After I get this to work, I intend to post my experiences for setting up SharePoint Integration with SQL and SP on separate boxes.

1. In the new reporting section under SharePoint application management in the Central Admin Console, the Grant database AND Set Server Defaults work when using the domain admin account, but not when using the SQLSPS service account I used to setup both SQL and SharePoint. Why can't I use the service account? Is the domain admin account now going to be used as a service account for accessing the sharepoint database?


This question remains unanswered as of yet.

2. Reporting Services configuration tool shows Sharepoint integration as red x when I create a new database in integration mode. (the service account SQLSPS and the Server object are members of the group WSS_WPG). If I switch back to native mode (the original reportserver database), the red x goes to a blue exclamation instead. Using Service Credentials or Windows credentials (as either the service account SQLSPS or as domain admin) doesn't change anything.


RESOLVED by using a domain user account for the ReportServer WebApp. Even though everything is installed on the same machine, it seems using the default of NETWORK SERVICE wasn't acceptable. Possibly because SharePoint is configured to allow additional machines in the farm?

3. http://servername:8080/reportserver will display Report Server information as it did before the integration on port 80, but http://servername/reportserver doesn't display anything through SharePoint.


Resolved. I needed to define a repository before I could view it (go figure). When I created a sharepoint site based on a report center template, created a data connection library and report library, and then referenced that by http://servername/sites/myReportCenterSite/myReportLibrary, I was able to see the equivalent of http://servername/reports (which is now disabled due to integration mode).

4. Unable to deploy to new report center sharepoint site I mention above using Visual Studio. I kept getting "A connection could not be made to the report server http://servername/sites/ReportCenter. Server was unable to process request. The request failed with HTTP status 503: Service unavailable (System.Web.Services). In Visual Studio, the project properties were: TargetDataSourceFolder = http://servername/sites/myReportCenterSite/myDataConnectionLibrary, TargetReportFolder = http://servername/sites/myReportCenterSite/myReportLibrary, TargetServerURL = http://servername/sites/myReportCenterSite/


Found these errors in the event logs on the server.

Event Type: Warning
Event Source: W3SVC
Event ID: 1021
Description:
The identity of application pool, 'ReportServer' is invalid. If it remains invalid when the first request for the application pool is processed, the application pool will be disabled. The data field contains the error number.

Event Type: Warning
Event Source: W3SVC
Event ID: 1057
Description:
The identity of application pool 'ReportServer' is invalid, so the World Wide Web Publishing Service can not create a worker process to serve the application pool. Therefore, the application pool has been disabled.

Event Type: Error
Event Source: W3SVC
Event ID: 1059
Description:
A failure was encountered while launching the process serving application pool 'ReportServer'. The application pool has been disabled.

RESOLVED the issue by changing the Application Pool used by reporting services from ReportServer to DefaultAppPool and changing the account DefaultAppPool used from NETWORK SERVICE to my service account SQLSPS. I have no idea why ReportServer is invalid, it was set to use the service account SQLSPS the same as DefaultAppPool is. Perhaps the reporting services add-on makes a change to invalidate this?

5. Attempting to read a SharePoint list using a SSRS report. This should be fun.

First, created a new custom list in the ReportCenter SharePoint sites I've been using and called it myCustomList. I added one item with a title of myCustomListItem1. I don't know if I need to do more than that for a simple test of reporting or not yet.

Second, configured new shared data source. Name = myCustomList1DataSource, type=XML, Connection String = http://servername/_vti_bin/lists.asmx (this URL is viewable in IE), Using Windows authenticaion.

Third, in VS2005 on a workstation in the domain, create new report item (report1.rdl). New dataset for report; Name=Report1DataSet, Data Source=myCustomList1DataSource (Shared), Command type = text, Query String = [See Queries and associated errors below]:

Initial query obtained from: Connecting SQL Reporting Services to a SharePoint List (David Wise)
http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx

Note: Queries when executing the dataset (which errors out) and when executing a query in CAML Viewer for the same information (which does work just fine) both initially return 401.1 and 401.2 errors (as viewed in Fiddler). Since the CAML query works, I have not tracked this down yet.


A. Original format from posting



<Query>
<Method Namespace=http://schemas.microsoft.com/sharepoint/soap/ Name="GetListItems"/>
<SoapAction>
http://schemas.microsoft.com/sharepoint/soap/GetListItems
</SoapAction>
</Query>


Parameter; Name => listName, Value => =myCustomList

Was NOT prompted to define the query parameters


- Gets this error: "An error occurred while setting the command text property of the data extension command. The XmlDP query is invalid. (Microsoft.ReportingServices.DataExtensions)."


- Advanced information from the error => 'http' is an unexpected token. The expected token is '"' or '''. Line 2, position 19. (System.Xml)

B. Changed: Placed the namespace URL in quotes (also tried with and without / in namespace after /soap)

<Query>
<Method Namespace="http://schemas.microsoft.com/sharepoint/soap/" Name="GetListItems"/>
<SoapAction>http://schemas.microsoft.com/sharepoint/soap/GetListItems
</SoapAction>
</Query>

Parameter; Name => listName, Value => =myCustomList (also tried Value => myCustomList) (no equal sign)

Clicked "!" to execute, and got prompted to define the query parameters
Entered Name => listName, Value => myCustomList

- Gets this error: "failed to execute web request for the specified URL (Microsoft.ReportingServices.DataExtensions)."

- Advanced information: <faultstring>Server did not recognize the value of HTTP Header SOAPAction: http://schemas.microsoft.com/sharepoint/soap/GetListItems/.</faultstring>


C. Try the query string that seems to work for Stramit CAML Viewer to read myCustomList

Stramit CAML query:
<Query xmlns="http://schemas.microsoft.com/sharepoint/soap/">
<OrderBy>
<FieldRef Name="ID" />
</OrderBy>
</Query>

Also tried
<Query xmlns="http://schemas.microsoft.com/sharepoint/soap/">
</Query>

And tried entering no query...

Parameter; Name => listName, Value => =myCustomList (also tried Value => myCustomList) (no equal sign)

Clicked "!" to execute, and got prompted to define the query parameters
Entered Name => listName, Value => myCustomList

- Gets this error: "failed to execute web request for the specified URL (Microsoft.ReportingServices.DataExtensions)."



- Advanced information: <soap:Fault><soap:Code><soap:Value>soap:Receiver</soap:Value></soap:Code><soap:Reason><soap:Text xml:lang="en">Server was unable to process request. ---&gt; Data at the root level is invalid. Line 1, position 1.</soap:Text></soap:Reason><soap: Detail /></soap:Fault>

RESOLVED. Went back to the query used in B above, and mysteriously it works now. This could be the "funny things happen" symptom I've been reading about. We'll see if it continues to function.

Here's what I've learned so far on Issue #5:

1. XML is confusing. XmlDP is even more confusing...whatever that is. Apparently it's new to/with Reporting Services in SharePoint integration mode?
2. There is far too little documentation regarding XmlDP and querying SharePoint lists from SQL Reporting Services.
3. According to http://msdn2.microsoft.com/en-us/library/ms159741.aspx: You must use the generic query designer to create the query. The query is not analyzed to identify parameters; therefore you must create parameters through the Parameter tab on the Dataset dialog box.

Tried this query:

<Query>
<SoapAction>http://schemas.microsoft.com/sharepoint/soap/GetListItems</SoapAction>
<Method Namespace="http://schemas.microsoft.com/sharepoint/soap/" Name="GetListItems" />
<Parameters>
<Parameter Name="listName">
<DefaultValue>myCustomReport2</DefaultValue>
</Parameter>
<OrderBy>
<FieldRef name="ows_Date" />
</OrderBy>
</Parameters>
</Query>
I was still prompted for the listName and the list returned with ows_Date still out of order. So maybe that proves this statement is true?
<translation: why make it convenient when it's already [somewhat] functional?>
4. When building the dataset, anything I place in the "Query string" box has to be enclosed in <query></query> tags or it errors out. I am trying to understand how to translate the CAML viewer query (which does work but isn't wrapped in query tags) into something that fits between query tags, and it hasn't gone well so far.
<translation: To be at one with your reports Grasshopper, you must understand xml>
5. According to http://srv1/sites/ReportCenter/_vti_bin/lists.asmx, "GetListItems" operation is supported
<translation: you're getting warmer...>
6. According to the soap output of my site http://srv1/sites/ReportCenter/_vti_bin/lists.asmx?op=GetListItems, I am only allowed to specify the following parameters: listName, viewName, query, viewFields, rowLimit, queryOptions and webID.
<translation: that and $3.00 will get you a cup of coffee>
7. According to http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx, only listName, viewName and rowLimit parameters are usable(?) (query and queryOptions may not be working properly with SSRS).
<translation: that kind of sucks>
8. When this started mysteriously working again, I tested using the "/" at the end of the namespace (wouldn't work without) and the "=" sign in front of the parameter value as defined on the parameter tab of the dataset (turns out to be optional).

As long as I can query SharePoint and get my list information back, I'm going to consider this issue closed and move on to actually using this information in a report. I'm sure that won't work right either, but why stop now?!

6. Ok, now that I can read SharePoint list data with SSRS, I need to try and actually do something with it.


A. Begin by setting up new data to report on


1. Create a new custom list (myCustomList2) and add a test record. This list will simulate the data we intend to submit to SharePoint using InfoPath, so it has a number of custom/created columns in it


2. Modify the working information from #5 above; add a new shared data source (myCustomList2DataSource), tell the dataset to use the new shared data source, change the information set in the parameter tab (Name => listName, Value => =myCustomList2) and test the dataset. Lucky me, it actually returned the record I entered on the first try.

B. Begin to build the report with the dataset returned

1. So, as I'm feeling good that it's actually reading the list in Step A without me threatening to destroy the machine, I look to the left in the Dataset results navigation pane in VS2005 and realize there are NO fields for me to choose to report on.
2. At this point, I have no clue what to do about getting this XML data into a report. Not that I have a large clue about SSRS otherwise, but I have at least been able to build SSRS reports when using a SQL database as the datasource. Fyi, http://msdn2.microsoft.com/en-us/library/ms159741.aspx states: "Reports can use data from XML documents and Web services, or embed XML in the query. There is no built-in support for retrieving XML documents from a SQL Server database.", in case anyone is trying to do that....

RESOLVED. Since the fields were not appearing automatically, I had started to add new fields to the dataset manually (if it doesn't work, beat it with a hammer, right?). I entered half a dozen or so fields, each one with the exact name as displayed in the query results, and then decided it would be fun to hit the refresh fields icon. As soon as I did that, all the fields shown in the query immediately appeared in the dataset and I was able to add them to a report. I don't know if I hit the refresh fields when working in issue #5, so I can't say if they are there now because of that, or because of adding some fields manually first, a combination of the two, or if it's just one of those mystery items I'm reading about with sharepoint reporting.

7. Rows are being returned even though they have NULL values (so far anyway), and most data is returning nicely for the bulk of the columns I created in the list I'm reporting on. Here are the current issues:


A. I have one column in my SharePoint list that is multi-lined text. If the text type is either rich text or enhanced rich text, the value returned in the query is formatted like this: "<div class=ExternalClassyadayada<div>My notes display here". If I set the column to be plain text, this doesn't happen. I will need to figure out how to filter that for my report.


RESOLVED. David Wise had some code listed at http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx that addressed this issue somewhat. I modified it to match my circumstances. Disclaimer: I'm not a programmer, so use this at your own risk.


function ExtractMultiLineText(myField as string) as string
dim strBegin as string
dim strEnd as string
dim myBegin as integer
dim myEnd as integer
dim myTextLength as integer
strBegin = "<div>"
strEnd = "</div>"
if myField = nothing then return ""
if myField = "" then return ""
myBegin = Instr(myField, strBegin) + Len(strBegin)
myEnd = Instr(myField, strEnd)
myTextLength = myEnd - myBegin

if myBegin < 1 then return myField
return mid(myField, myBegin, myTextLength)
end function

B. I have two columns in the SharePoint list that are set as number values with 0 decimal places. When I query those however in SSRS, they return with the number plus like 12 zeroes behind the decimal. Not a major issue, but I'll put it on the list anyway.


RESOLVED. Used the Int() function; =Int(Fields!ows_myProblemNumber)

C. If I go to "/_vti_bin/lists.asmx?op=GetListItems", it appears from the sample soap output that I am allowed to ask GetListItems for is: listName, viewName, query, viewFields, rowLimit, queryOptions and webID. As I mentioned in issue #5, according to http://www.sharepointblogs.com/dwise/archive/2007/11/28/connecting-sql-reporting-services-to-a-sharepoint-list-redux.aspx, only listName, viewName and rowLimit parameters are usable(?) and query and queryOptions may not be working properly with SSRS.

So, if I can't put anything other than this in my query string;

<Query>
<Method Namespace="http://schemas.microsoft.com/sharepoint/soap/" Name="GetListItems"/>
<SoapAction>http://schemas.microsoft.com/sharepoint/soap/GetListItems</SoapAction>
</Query>
and I only have a couple parameters to pass on top of that, then it appears to me that my options for filtering the amount of data returned from the SharePoint list is to figure out a way to do it with expressions in the parameters or in the report itself. Am I missing something? Is this really all I get to work with out-of-the-box?


More to come...


==================================
Installation steps taken to build the server VM:
==================================

(Using VirtualPC 2007)
1. Build OS (2003R2SP2) and promote to DC

1a. Create domain user service account SQLSPS
2. Prep for SQL

2a. Install ASP.NET, IIS (www) and .NET 2.0
3. Install SQL/SSRS 2005 Std

3a. Verify SSRS works
3b. RS config tool shows SP integration as blue exclamation
3c. Use service account SQLSPS for anything requiring Windows credentials
4. Install SQL2005 SP2

4a. Verify SSRS works
4b. RS config tool shows SP integration as blue exclamation
5. Prep for SharePoint

5a. Install .NET 3.0
6. Install MOSS2007 Enterprise and configure

6a. Webapps, SSP and anything else use svc acct SQLSPS
6b. Move Default website to port 8080 and re-activate (SharePoint stopped the site)
6c. Verify SSRS works on 8080
7. Install Reporting Services Add-in
8. Create new RS database in integration mode (with service credentials)

8a. RS config tool shows SP integration as red x
9. SP central admin /application management / manage integration settings

9a. reports server = http://srv1:8080/reportserver (since default port has been moved to 8080)
10. SP central admin /application management/grant database access

10a. using the FQDN, confirm servername and default instance - click OK
10b. Prompted for an account to use to retrieve information; svc acct SQLSPS did not work, domain admin did though
11. SP central admin / application management/set server defaults

11a. Accepted all defaults
12. Verify reportserver answers at http://srv1:8080/reportserver (via reportserver AppPool and DefaultAppPool)
13. Changed the application pool identity for the ReportServer AppPool from Network Service to the domain user service account I used for all SQL and SharePoint configurations (SQLSPS) and rebooted. The red x for sharepoint integration in the RS configuration tool is now a green checkmark.

View 7 Replies View Related

Master Data Services :: Connect To MDS From Excel Addin

Jun 16, 2015

I have an issue with MDS (Master Data Services for ONE platform). When I try to connect to MDS from Excel addin, I get the error - please see the attachement.

View 2 Replies View Related

Reporting Services Addin - Set Server Defaults Error

Sep 18, 2007

Hey All,

I installed Reporting Services Add-in with no problems on a Virtual server that already hosts MOSS 2007 and configured everything that was stated in documentation. The Report server Url works fine..like http://myserver1:802/ReportServer and I can see the contents when I type this url.

However, when I go to Central Administration and click on "Set Server Defaults"...I am getting a "401.1 Unauthorized..." error.I setup the Manage Integration to TrustedAccount and the Grant DatabaseAccess to the account that is the Server.Farm and local administrator.

In the Reporting Services Configuration, I used SSRSWebAccount for WebService and SSRSWindowsAccount for WindowsService and the RSAppPool which is the ApplicationPool for ReportingServices Web Site uses the SSRSWindowsAccount only.

Anybody..please help.

Thanks,
Vedala

View 4 Replies View Related

Errors In Table Analysis Tools For Excel DataMining AddIn

Mar 2, 2007

It's an error "The 'MINIMUM_DEPENDENCY_PROBABILITY' data mining parameter is not valid..." always I try to run Analyze Key Influencers Tool. How it's possible to fix it?

View 5 Replies View Related

Master Data Services :: How To Stop Excel Addin From Being Disabled

Apr 3, 2012

We are using Office 2010 on Citrix with the RCO Master Data Excel addin. I am getting many calls from users that the Addin has disappeared from the Excel menu. Can re-enable it by going to files->Options->Addins and manage COM addins. Have not been able to work out why it becomes disabled. Any registry setting that I can use to stop it from being disabled?

View 4 Replies View Related

Problem - SQL 2005 Reporting Services Addin For Web Developer 2005 Express....

Dec 8, 2007

Hello,

I'm trying to make some reports using the sql 2005 reporting services addin for Visual Web Developer Express 2005. I download the add-in here. So far it installed "successfully". The problem i have is when i try to add a datasource to the report at "Report > Data Sources... " it gives me an error saying: "The system cannot find the file specified."

Another Error it gives is that when I try to drag a DataSet field from the Website Data Sources toolbox tab the visual web developer crashes :/.

An observation that I don't know if this is ok is when I create a new Data Source it creates an App_Code folder inside where my report is /Reports/ and there it saves the DataSet. Just an observation...


This is my development enviorment:

Laptop:

Windows Vista Home Premium (Up to date)
Microsoft Visual Web Developer 2005 with Service Pack 1
Reporting Add-In for Microsoft Visual Web Developer 2005 Express

Server:

Microsoft Windows Server 2003
IIS 6.0
ASP.NET 2.0
Microsoft SQL Server 2005 Express
Reporting Services for SQL Server 2005 Express


Here are some pictures of the erros:


Error 1

Error 2

Please could someone help me fix this?

Thanks in advance.

View 3 Replies View Related

Sharepoint

Aug 15, 2007

Anyone ever heard of or use this, and how does it talk to sql server?

View 14 Replies View Related

SQL With Sharepoint

Jun 16, 2006

Hi all, we have a SQL 2000 database which is for recording job information. we are trying to do a sharepoint page that will show all outstanding jobs with conditionl formating to hilight overdue jobs red. we have managed to do this by date with no problem but we are unable to do this by time.

We have created a view that sharepoint looks at for the needed fields. the job due time field only has the time entered in which means the default date of 01/01/1900 gets entered by the system.

we need away that the only the time is outputted in the sharepoint view and a way to apply conditional formatting to this field in sharepoint and a way to compare the this time to the current system time.

I hope this makes sense, as we are complete novices when it comes to SQL. Please ask if you need any more information.

Any help or a point in the right direction would be deeply appriciated.

View 1 Replies View Related

RS In Sharepoint 2007

Jan 22, 2007

Sharepoint Server Portal 2007, MSSQL 2005, Reporting Services

When I try to integrate Reporting Services in Adminitsrator, for url of RS I write this: http://servername/ReportServer/ and click OK.

But when I try to go to 'Set Server defaults' or 'Managed Shared Shedules' I get this:

Server was unable to process request. ---> Client found response content type of '', but expected 'text/xml'. The request failed with an empty responseWhat should I Do ?

View 1 Replies View Related

Sharepoint SQL Problemas

Dec 11, 2006

Hi,
I had already setup a SharePoint 2007 Server with a SQL Server 2005 in the same machine.
I cloned the full computer and now my SharePoint clone is pointed to use the old SQL
Server.

How I change my cloned SharePoint to use my cloned SQL Server?


The old configuration diagram
OLD_COMPUTER - SharePont 2007 --> (pointed to) OLD_COMPUTER SQL Server
OLD_COMPUTER - SQL Server


The actual configuration diagram
NEW_COMPUTER - SharePont 2007 --> (now pointed to) OLD_COMPUTER SQL Server
NEW_COMPUTER - SQL Server


The desired configuration diagram
NEW_COMPUTER - SharePont 2007 --> (pointed to) NEW_COMPUTER SQL Server
NEW_COMPUTER - SQL Server

View 1 Replies View Related

SharePoint Integration

Feb 7, 2007

I originally installed SQL Server 2005 and configured Reporting Services to run on a different port and website and all worked fine. I can access it via localhost:15540/reportserver and also use BI Development Studio to creat and publish reports.

I updated to SQL Server 2005 SP2, selected SQL Server integration on Reporting Services Configurator, created a new Report servcies database. Now when I go to localhost:15540/reportserver, the reports I had previously had available do not show... that may be ok?

However, I go to Sharepoint 3.0 Central Admin, no entry for Reporting Services show under App Management. Should it?

I also notice that link localhost:15540/reports no longer work... Where should I be able to go to get access to the same functionality.

I guess I am a little confused as to what the integrated mode should do for me. All I really wanted the capability to do was use the report viewer from inside sharepoint.

Thanks so much for any help

View 5 Replies View Related

Installing Sharepoint RS Add In

Aug 30, 2007

hey guys, have a problem with installing the sharepoint 2007 add in for Reporting services.

It goes through the install and ends with that the install was interrupted. The error is



SSRSCustomActionError: SharePoint is installed, but not configured.


I have looked this up on the net, but havn't found any answers. I have made sure the site collection admin is the same as the user trying to install the add-in, but it just keeps failing.

I have reporting services on 1 machine and moss 2007 on a different server,

it is a clean install of moss 2007 and is fully configured and operational.

the inetpub directory is on the D: instead of the C:.. dont think this would be an issue

does anyone have any ideas on why this is happening and what i can do to fix it.


many many thanks to anyone who can help me.

Scotty

View 3 Replies View Related

Installation And Sharepoint

Sep 12, 2006

I have been trying to install SRS to a machine that has Sharepoint already installed on it.  I have gone through this article:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/RSinstall/htm/gs_installingrs_v1_9fdy.asp

I used the rsactivate tool and it said the command completed successfully.  I tried to verify that everything was setup by going to the site http://localhost/reportserver and I get this error:


Server Error in '/ReportServer' Application.


Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: File or assembly name Microsoft.BusinessFramework, or one of its dependencies, was not found.

Source Error:





Line 73: <add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule" />
Line 74: <!--<add name="Session" type="System.Web.SessionState.SessionStateModule"/>-->
Line 75: <add name="EnterpriseInitializationModule" type="Microsoft.BusinessFramework.Security.EnterpriseInitializationModule,Microsoft.BusinessFramework" />
Line 76: <add name="Session" type="System.Web.SessionState.SessionStateModule" />
Line 77: </httpModules>
Source File: c:inetpubwwwrootweb.config    Line: 75

Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.BusinessFramework' could not be loaded.





=== Pre-bind state information ===
LOG: DisplayName = Microsoft.BusinessFramework
(Partial)
LOG: Appbase = file:///D:/Program Files/SRS/MSSQL/Reporting Services/ReportServer
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===

LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind).
LOG: Post-policy reference: Microsoft.BusinessFramework
LOG: Attempting download of new URL file:///c:/windows/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files/reportserver/00b4b1a7/c716c103/Microsoft.BusinessFramework.DLL.
LOG: Attempting download of new URL file:///c:/windows/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files/reportserver/00b4b1a7/c716c103/Microsoft.BusinessFramework/Microsoft.BusinessFramework.DLL.
LOG: Attempting download of new URL file:///D:/Program Files/SRS/MSSQL/Reporting Services/ReportServer/bin/Microsoft.BusinessFramework.DLL.
LOG: Attempting download of new URL file:///D:/Program Files/SRS/MSSQL/Reporting Services/ReportServer/bin/Microsoft.BusinessFramework/Microsoft.BusinessFramework.DLL.
LOG: Attempting download of new URL file:///c:/windows/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files/reportserver/00b4b1a7/c716c103/Microsoft.BusinessFramework.EXE.
LOG: Attempting download of new URL file:///c:/windows/microsoft.net/framework/v1.1.4322/Temporary ASP.NET Files/reportserver/00b4b1a7/c716c103/Microsoft.BusinessFramework/Microsoft.BusinessFramework.EXE.
LOG: Attempting download of new URL file:///D:/Program Files/SRS/MSSQL/Reporting Services/ReportServer/bin/Microsoft.BusinessFramework.EXE.
LOG: Attempting download of new URL file:///D:/Program Files/SRS/MSSQL/Reporting Services/ReportServer/bin/Microsoft.BusinessFramework/Microsoft.BusinessFramework.EXE.





Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

 So, I added the dll to the bin directory inside ReportServer...I get this error:
Server Error in '/ReportServer' Application.


Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Required permissions cannot be acquired.

Source Error:





Line 73: <add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule" />
Line 74: <add name="Session" type="System.Web.SessionState.SessionStateModule"/>
Line 75: <add name="EnterpriseInitializationModule" type="Microsoft.BusinessFramework.Security.EnterpriseInitializationModule,Microsoft.BusinessFramework" />
Line 76: </httpModules>
Line 77: <globalization fileEncoding="utf-8" />
Source File: c:inetpubwwwrootweb.config    Line: 75





Version Information: Microsoft .NET Framework Version:1.1.4322.2300; ASP.NET Version:1.1.4322.2300

 

So, I added code groups to the .Net 1.1 security configuration...the same error is displayed.  If I comment out the offending http module in the sharepoint web.config, it all runs.  However, this is not acceptable because it seems to affect my Business Portal site.

Anyone know how to solve this?

Thanks,

Tom

View 2 Replies View Related

Sharepoint Integration

Mar 1, 2007

Hi all,



I've tried 3 times to integrate RS in Sharepoint and I always have the same result. I can't see the new section in sharepoint central administration under application management. I didn't get any errors while installing any of the components.

RS and Sharepoint are on the same machine and I carefully followed the step to integrate RS in Sharepoint



Can someone help me on this?

thx



Fred

View 11 Replies View Related

Database Experience With Sharepoint?

Apr 14, 2008

It looks like I'll be assigned with development and database management utilizing Microsoft Office Sharepoint Services and saw that there are some issues as it can become quite unwieldy.

I was wondering what difficulties to expect from MOSS and/or Sharepoint in terms of managing and backing up. Any tips or suggestions?

View 2 Replies View Related

Backup Sharepoint 2007

Jun 12, 2008

I know this is not SQL server related. Do anyone know good Third-party tools to backup sharepoint 2007? I have looked at www.avepoint.com and ideras tools but didn't find price listings. I am looking which has reasonable price and efficient.
Only xpurt ownly

View 4 Replies View Related

SharePoint Services And SQL Express

Dec 22, 2005

Hi, I'm new to the forum and also to SQL Server.
Has anybody implemented SharePoint Windows Services on top of SQL Express? I'm trying just that, but i'm encountering some problems when trying to enable Full-Text search. The configuration page for this option says that the database i'm running on does not support full-text search.
Thanks in advance,

Ulises

View 4 Replies View Related

Sharepoint And SQL Express 2005

Jan 9, 2008

I found out the battery in my UPS isn't working anymore. My server down a couple of times with power outages before I figured out it wasn't doing its job.

I make backups of my Sharepoint databases using the gui interface in Sharepoint, so I have backups and have used them for a couple of the outages.

What I was wondering (I'm a newb to SQL), if I do a checkdb and get no errors when the databases (sharepoint_config and sharepoint_data) are marked suspect, is there an easy way to get them back online without using the backups. The only reason I ask, there is data entered in the 23hrs (daily backups) since the last backup that I wouldn't mind keeping.

Also, I seem to have gotten (from reading some of the posts here) my sharepoint_config stuck in emergency mode and can't find a post on how to get it back to normal/online mode ;)

-Sony

View 1 Replies View Related

How To Integrate Sql Queries Into Sharepoint

Mar 28, 2008

Hi All,

i have written so many queries in sql 2000/2005 and now i have to integrate them into sharepoint which i have never done..can anyone guide me how it can be done? or where i have to post this question?
the correct forum?

any help would be appreciated.
thanks

View 1 Replies View Related

Help Please. Sharepoint+Access Db + Infopath

Jun 10, 2007

Hi guys. Im having alot of trouble with this. I have created a simple access database, uploaded to a doc library on a sharepoint site. Then I made a infopath form based on this by using the url: //207.245.47.37/sites/Safety_and_Training/ai/db2.mdb

I succeeded in creating the form. I then published it onto the sharepoint site. Now, when I try to fill out the form so the database can be filled in, I hit submit and it opens up a ADO warning telling me that the website is using my identity to connect to the datasource, I hit ok and then I get another window saying "Please enter MS JET OLE DB Initialization." In the fields it has 1) Datasource is \207.245.47.37sitesSafety_and_Trainingaidb2.mdb, the 2)username is Admin, 3)password is blank, 4)provider string is blank and the 5)open mode is on DB_Mode_Readwrite.

1. One thing I tried is in the username and password I give my administrator login as CorpdynatecRGill, and then the password I always use to login onto the site. It then gives me:


InfoPath cannot connect to the data source.
Not a valid account name or password.



2. Next thing I try is just leaving the username as admin and password blank but then I get the message:

InfoPath cannot connect to the data source.
The Microsoft Jet database engine cannot open the file '\207.245.47.37sitesSafety_and_Trainingaidb2.mdb'. It is already opened exclusively by another user, or you need permission to view its data.

I think it might have something to do with the permissions, but nothing has been working yet. Please help me.

View 2 Replies View Related

Serving Up Reports Without Sharepoint

Feb 6, 2007

Hello,

Sorry for the newbie question...

Is there a way to "serve" up reports in a SharePoint-like way without using SharePoint?

I am part of a team of ASP.NET developers that are writing our own pages, but I haven't been able to find information about Reporting Services 2005 in ASP.NET and/or using Web Parts on our own pages.

Any information about this would be greatly appreciated.

Thank you.

-Gumbatman

View 3 Replies View Related

Getting Data From Sharepoint Lists

May 15, 2006

Hi,

I'm trying to get data from WSS lists by web services. I think there are two ways:

- using SSIS standard components (Web Service Task) and
- creating a custom source adapter.

My problem with the Web Service Task is, that the WSS method GetListItems has some non-standard parameters (see part from wsdl-file below). Thus, after selecting the method in the editor an clicking on "Ok", I get the error message "The selected Web method contains unsupported arguments". I think the problem is the missing type-attribute.

<s:element name="GetListItems">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="listName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="viewName" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="query">
<s:complexType mixed="true">
<s:sequence>
<s:any />
</s:sequence>
</s:complexType>
</s:element>
...

My question: Is there a way to extend the Task to handle such parameters?

View 1 Replies View Related

RS Web Parts On SharePoint 2007

Feb 20, 2007

Hi,

I'm having troubles connecting the webparts on SharePoint 2007. I installed the RSWebParts package from SQL Server 2005 Reporting Services on my MOSS 2007 box. The installation went smoothly and I can add both Report Explorer and Report Viewer on a page. But when I try to connect RE to RV I get the following error:


An unexpected error has occurred.

Web Parts Maintenance Page: If you have permission, you can use this page to temporarily close Web Parts or remove personal settings. For more information, contact your site administrator.

So I have to go to the maintenance page and remove the web parts.

Have anyone managed to bypass this and make them work together?

Thanks,

View 1 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved