You’re offline. This is a read only version of the page.
240
Background:
Our client has a single server (I recommended against this) with SQL 2016 and GP installed on it and they are using it as such.
1. They want to have a full install of CRM on this same box, very few users.
2. Reporting Services is already installed and was running under the local service account, but it was not configured.
3. I configured SSRS by your normal create the databases, hit the apply button a few times etc, all went well, I can log in etc, no SSL, port 80, defaults stuff.
4. I installed CRM, and installed the Reporting Extensions (all the 8.2 versions mind you after the initial 8.0 install of CRM, all went fine). It published the reports, and logging directly into SSRS I can see them all, looks normal. Installed CRM on port 80 as well, no SSL.
5. When I attempt to view one of the out of the box reports, any of them really, I get a couple of different errors in the event log. NOTE: (I'm attempting to view them from that server itself, not sure if that's an issue)
6. I tried setting the service account (through ssrs configuration manager) to just be network service, I checked and it is using NTLM in the config file, which is fine, client is not using ADFS or anything. Simple client and I thought for sure this simple setup would most likely work.
7. Running an ootb report, gives the following error in the event application log.
The first error received in the event log is given (from MSCRMReporting):
Web service request GetDataSourceContents to Report Server crmserv/.../ReportService2010.asmx failed with SoapException. Error: The report server has encountered a configuration error.
8. If I check the security event log at the same time, the below shows up. I believe this is where the CRM Server itself is trying to take my user creds and pass it on. Same error if the service account for SSRS is changed to Network Service or Local System etc.
An account failed to log on.
Subject:
Security ID: NETWORK SERVICE
Account Name: CRMSERV$
Account Domain: MPA-PSI
Logon ID: 0x3E4
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Name:
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xC000006D
Sub Status: 0xC0000064
Process Information:
Caller Process ID: 0x2d64
Caller Process Name: C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer\bin\ReportingServicesService.exe
Network Information:
Workstation Name: CRMSERV
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Authz
Authentication Package: Kerberos
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
I know i'm missing something probably pretty simple, again, no need for anything fancy here for this particular client. Thanks ahead of time for any input anyone has.
*This post is locked for comments
I have the same question (0)
You should configure it with a service account. Don't use Network Service or System for it.
Share
Report
All responses (
Answers (
