When I click on the help icon in my Microsoft Dynamics CRM 2011 installation, I get the following very weird result:
It appears as if the help page loads itself, and when I look at my requests through Fiddler, this is indeed what happens. If I go to the help page URL directly (without using the help icon), it works fine. Any idea what might cause this behavior?
This problem is caused by a misconfiguration of the CRM installation. To verify this, execute the following query on your Dynamics CRM database:
SELECT [HelpServerUrl]
FROM [MSCRM_CONFIG].[dbo].[ConfigSettings]
The value returned by this query will looks like this: https://<yourhostname>/help/default.aspx/ The help server URL thus includes the path to the /help/default.aspx page. However, if you click on the help icon, Dynamics CRM will append /help/default.aspx/ to the help server URL. This causes the weird, nesting behavior. It also explains why going directly to the help page does not exhibit this behavior.
The solution is simple: edit the [HelpServerUrl] value in the [ConfigSettings] table and remove the /help/default.aspx part. This will leave just the base server URL in the setting. The final step is to recycle the application pool of the website (as the server URL is cached) and everything works!
Related
SharePoint Online: Until yesterday, I was able to use the standard Embed web part to display an iFrame to my SSRS Report server that included the control settings in the URL to hide toolbar, etc.
Like this:
<iframe src="https://reports.mydomain.com/ReportServer?/Reports/WallChart_GP&rs:Command=Render&rc:Toolbar=false&rs:ClearSession=true" height="400" width="300"></iframe>
Today, that is suddenly resulting in "Reporting Server Error: The operation you are attempting on item '/' is not allowed for this item type. (rsWrongItemType)". However if I put the URL directly into a browser I get the correct result... report with no toolbar.
When I switch the SharePoint page to edit mode and look at the Embed web part, I see that it's changing my & to & plus "amp;" for HTML formatting. If I paste that modified string into a separate browser I do still reach the report but the server ignores at least some of my commands in that I then see the report server toolbar despite setting it to false. So I don't know if it's always changed my URL like that, or if that is indeed the source of my problem. But I had not even re-published my pages in SharePoint.
If I put an embed string in the SharePoint web part that does not attempt these report server commands, I do get the report as desired. For example this displays my report in the SharePoint web part (but with the toolbar that I'm trying to avoid showing):
<iframe src="https://reports.mydomain.com/Reports/Pages/Report.aspx?ItemPath=%2fReports%2fWallChart_GP" height="400" width="300"></iframe>
The thing that has me bring this here is the fact that it was working up until yesterday. Nothing was changed on either end. I suppose Microsoft Support may be the correct avenue but I'm concerned that I will just be told that I can't do it without regard to the fact that it worked all along.
Any insight into why this is now different or what I can do to resolve the problem?
Background
I have an ASP.Net Core v2.0 web application that has the [HttpGet] attribute above action results that don't need to accept a post.
I created a spreadsheet with a list of pages on the website to my marketing team, along with a column of hyperlinks that link directly to each page on the website.
Example Spreadsheet:
Issue
Once the marketing team started clicking on the links in the spreadsheet, I started to receive 404 errors via email (configured using NLog) although the page did still load for the user.
Troubleshooting
I troubleshooted this and uncovered that the issue was down to the [HttpGet] attribute. If I take the [HttpGet] attribute out, clicking on the links in the spreadsheet doesn't generate a 404 error.
The site doesn't generate 404 errors when loading the page (s) via the browser.
I installed fiddler and it looks as though Excel is using the "CONNECT" method.
Fiddler screenshot:
I thought this could be the issue as it's not a GET but when I access a page within Chrome, it also shows using the "CONNECT" method in fiddler.
I'm looking to see if anyone else has had this issue and if they got around it? Do I need to add another attribute alongside [HTTPGet] to stop Excel or other 3rd party software causing a 404?
I've resolved my own issue.
For anyone else that has this issue the fix is to put [HttpGet, HttpHead] as the attribute. If you have a custom route then add another attribute underneath:
[Route("[controller]/custom-action")].
For info, I got to the bottom of this by using the logs from the drop down ASP.Net Core Web Server in the output window in Visual Studio. I could see that when the link was first being requested by Excel, it was using the HEAD method rather than the GET which is why a 404 error was being fired.
Hope that helps someone down the line.
SharePoint web site = http://myexample:3500
SharePoint tester (admin on domain, admin on SharePoint site collection) = IAmKyle
Alternate Access Mapping: I left it at the default which is http://myexample:3500 maps to itself, and the zone is "default".
My code was deployed as a farm solution and my .dll is in the GAC. I activated a feature on my site collection (url is above). What the code does is, when the user updates a SharePoint item, my code executes a LINQ query finding "related" items. Then the related items are updated. Here are the errors I get:
On Windows Event Logs:
Error loading and running event receiver [my receiver assembly]. Object reference not set to instance of an object.
On SharePoint ULS event logs:
Same error as I see in Windows Event logs. Also, I was getting errors about "alternate access mapping" not being configured for http://myexample:3500 but I'm not getting them anymore. Don't know why, I haven't changed anything.
On IIS logs
Getting some 401 responses for pages that I should be able to access. But, it only shows the tail end of the page in some cases e.g. "/mysite/mypage" so I'm unsure what the full URL is.
These errors are very confusing, my code 100% works on my test system. What network or sharepoint configurations should I be looking for? I'm assuming my code itself works fine considering that it does work on my test environment. Of course, I have more permissions on test since my username on test is the user who created the farm.
Thanks.
Do you get these errors when trying to activate the feature or when actually making a change to a list item?
Also, have you tried attaching the VS debugger to the process and having a look at what is going on?
I have deployed CRM and installed the reporting extensions component successfully on the SSRS server with rollup2 (server and router match this) - I have separate servers for CRM , SQL and SSRS. The out the box reports work ok but the custom reports present an error "rsProcessingAborted" which to me sounds like permissions. I have read a number of articles relating to pepople with the same issue and have tried all possible fixes but still no joy.
SSRS runs under a svc_sqlserver acccount and this account has permissions in the DB
the datasources have all been created successfully and the custom reports are using the MSCRM_FetchDataSource which is configured with type Dynamics CRM Fetch and credentials supplied by the user running the report. The connection string says CustomerServicesCE which is the correct OrgsanisationID (as found within developer resources) - i have tried clearing this connection string, adding the server url, all possible combinations with no joy.
Within SSRS i cannot view the report, it says "cannot access the CRM datasource" - i read somewhere you need to enter the GUIDs systemuserid and organisationid as username and pwd but still no joy.
I tried amending one report to use the samedatasource as the out the box reports that work but still no joy which is the MSCRM_DataSource...................am i missing something?
These reports have come from another supplier - i don't mind how they are displayed (Fetch or otherwise) i just need them working!
interestingly i do get them working on my Development environment (after getting the same error) and to my eyes the setup looks identical!
thanks for any help
richard
the answer was to create an spn as
setspn -a http/crmservername domain\accountCRMrunsunderrIIS
A changed Windows authentication to Forms authentication. Using the following example.
I added a user with Web Site Administration Tool. Finally I added this user as Site Collection Administrators and the user is recognized by SharePoint. Happy with that is started my WSS site in the browser but when I try to Sign in using this sign in form it is not working. Returns to this form after the submit (//spvm:100/_layouts/login.aspx?ReturnUrl=%2f_layouts%2fAuthenticate.aspx%3fSource%3d%252f&Source=%2f)
I have been scanning my Eventviewer but no succes for any comment what tells me what I am doing wrong. Maybe some of you guys can help me out?
Once you are redirected to this page, try navigating to http://spvm:100. Sometime I get this kind of case where I move make to the root, then it works. I really didnt know the reason why sometime it behaves like that.
I had the same issue. I found that something was wrong with my browser's settings. I tried to log in with another browser (Firefox) and that worked for me.
I don't know yet what was wrong with my IE7's settings, on another machine I could log in to a forms auth site without any problem.