Share
Report
2Description
Hi Everyone,
I am facing an issue with Dynamics CRM On-Premise 9.1.44 where Report Wizard (FetchXML) reports are failing only in the DEV environment, while the same reports work correctly in the STAGING environment
Environment
- Dynamics CRM On-Premise 9.1.44
- Windows Server 2022
- SQL Server 2022
- SSRS 2022
- CRM Reporting Extensions installed
We have two environments:
STAGING (Working)
- CRM Server: usxx-xxxxxcrms
- SSRS Server: usxx-xxxxx01s
DEV (Not Working)
- CRM Server: usxx-xxxxxcrmd2
- SSRS Server: usxx-xxxxx02d
Both environments are running the same CRM version (9.1.44).
Issue
Only Report Wizard (FetchXML) reports fail.
For example, an "Activity Report" created using the CRM Report Wizard.
When executing the report from CRM, the following error is displayed:
Reporting Error
The report cannot be displayed.
(rsProcessingAborted)
However:
- All Out-of-Box reports work correctly.
- SSRS itself is working.
- CRM is accessible.
- Organization Service is accessible.
- Only FetchXML/Report Wizard reports fail.
SSRS Log Error
Microsoft.Crm.CrmException: An unexpected error occurred.
System.ServiceModel.Security.SecurityNegotiationException:
A call to SSPI failed.
System.Security.Authentication.AuthenticationException:
A call to SSPI failed.
System.ComponentModel.Win32Exception:The target principal name is incorrect
The exception occurs while executing:
Microsoft.Crm.Reporting.DataExtension
SdkMetadataProvider.GetEntity()
What has already been verified
CRM
- CRM version is identical to STAGING.
- Report definition is identical.
- CRM Reporting Extensions are installed.
- CRM Organization Service is accessible.
Opening the following URL works:
http://xxxx-wwssxxxxx:XXXX/CRMD365/XRMServices/2011/Organization.svc
CRM App Pool
CRM Application Pool runs under:
AZGXXXXX\XXXCRM.SVC
SSRS
SSRS Service runs under:
AZGXXXXX\xxxcrxinstall.svc
Both DEV and STAGING use the same service accounts.
Reporting Extension
Verified the Reporting Extension version:
Microsoft.Crm.Reporting.DataExtension.Server.Fetch.dll
Version
9.0.2.3034
Version is identical in STAGING and DEV.
SPN Verification
For CRM App Pool account:
setspn -L AZGXXXXX\XXXCRM.SVC
Output:
HTTP/usxx-xxxxxcrms
This is the STAGING CRM hostname.
Checking DEV hostname:
setspn -Q HTTP/usxx-xxxxxcrmd2
Output:
No such SPN found
Checking forest:
setspn -F -Q HTTP/usxx-xxxxxcrmd2
Output:
No such SPN found
However, when trying to register the SPN:
setspn -S HTTP/usxx-xxxxxcrmd2 AZGXXXXX\XXXCRM.SVC
I receive:
The operation failed because SPN value provided for addition/modification is not unique forest-wide.
Error 8647
This seems contradictory because the SPN cannot be found, yet it also cannot be added.
Duplicate SPNs
setspn -X
Output: Found 0 group of duplicate SPNs.
IIS
- Windows Authentication enabled.
- CRM App Pool identity verified.
- Organization Service accessible.
SSRS Configuration
Verified:
- Service Account
- Database
- Web Service URL
- Web Portal URL
Everything matches the working STAGING environment.
Additional Checks
- DLLs were unblocked.
- CRM Reporting Extensions rechecked.
- Registry entries compared with STAGING.
- Same CRM version.
- Same Reporting Extension version.
- Same CRM configuration.
- Same service accounts.
One important observation
Both STAGING and DEV use the same Active Directory service accounts:
CRM App Pool
AZGXXXXX\XXXCRM.SVC
SSRS Service
AZGXXXXX\xxxcrxinstall.svc
This makes me think the issue may be related to the DEV CRM hostname (usxx-xxxxxcrmd2 ) rather than the service accounts themselves.
Questions
- Why would setspn -Q report that the SPN does not exist, but setspn -S fails with Error 8647 stating that it is already present forest-wide?
- Could this indicate a stale AD object or AD replication issue?
- Since the same service accounts work in STAGING, could this instead be related to the DEV hostname or Kerberos authentication to that specific server?
- Has anyone experienced this issue with Dynamics CRM 9.1 on Windows Server 2022 where only Report Wizard (FetchXML) reports fail while all other reports work?
- Is there any additional CRM Reporting Extension or SSRS configuration that should be compared between the working and failing environments?
Any suggestions would be greatly appreciated.
All responses (
Answers (
