Lead and Contact forms blank after upgrade to CRM 2015 - dynamics-crm-2013

Since we upgraded a CRM 2013 organization, certain user roles get blank forms (nothing below the command bar) when they try to view a contact or lead record in the system.
The role that they are assigned to has read permissions for both of these record types. Users with the system administrator role have no problem opening the form. There is no error message that pops up or is in the console of the browser developer tools. This is happening in all three major Windows browsers.

It turns out that the fix was to add the Read privilege on the Campaign entity in the role. I don't know if this is related to the Last Campaign Date field on the records, but that fixed the issue.

Related

CRM 2016 Reports: Some dataset are blank when the report is ran with a specific user

I have a report on CRM 2016 which runs perfectly when it is launched with admin user. However, when we launch it with a normal user, all the datasets are displayed perfectly, except for 1 dataset (which was added lately to the report). To note that all the stored procedures used by the datasets (including this new one) have the same security roles on the SQL database. In addition, when I run the report from the visual studio, all the datasets are displayed as well. Can someone please help?
Solved. It was a security role issue on the business unit level

#1044 - Access denied for user 'buriedse'#'%' to database 'buriedse_root'

i tried everything possible to fix this but nothing worked for me ,pls help me to create a table on my database .
AS your question title says, the error is a clear problem with your user autentication. This problem may be due to a very large list of causes, but I will give you what in my humble opinion is a quick troubleshooting that may lead you to solve this problem:
First of all, check the permissions of your user on the specified database. Using SQL Server Management Studio, right click your user, properties, then user mapping. Right there you have to check for the correct database mapping and the desired role.
Check server authentication mode, to see if it is on mixed mode. In many cases, I´ve seen many installations where the authentication is set to windows only, and users keep getting this message having the correct permissions on user and correct mappings.

Customize Authentication Dropdown in Business Objects 4.1 BI Launch Pad

Looking for a way to customize the authentication dropdown presented to users when logging into the BI LaunchPad application, version 4.1 (known as InfoView in prior versions). Currently, users are asked to make one of the following choices: Enterprise, LDAP, Windows AD, SAP, JD Edwards Enterprise, Oracle EBS, PeopleSoft Enterprise, and Siebel7.
The BILanchPad.properties file has already been modified as follows:
authentication.visible=true
authentication.default=secEnterprise
This was done to allow the users to choose (some are logging in with Windows AD, most with Enterprise) their authentication type. My goal is to remove the extra options (LDAP, SAP, etc.) so that if a user tries to choose their authentication type, only the two 'valid' options will be visible to them.
Again, I've already set the properties for the default and making the dropdown visible. I'm not interested in changing those, just in limiting the options within the list.
Is there any way to customize what authentication types appear in this drop down?
Authentication Types correlate to what was selected at the time of installation. If you see JD Edwards, Peoplesoft, Oracle EBS, Sievel, etc. then those database types were selected during the time of installation. You can perform a Modify install to add\remove these options.
If they are already listed in the drop down box, you can remove them form the selection list by going to Authentication > choosing the Authentication Type (ie. Oracle EBS), and Disabling the authenticatoin type. This should exclude it from the drop down list.
If you see these authentication types listed in the drop down box, but you do NOT see them listed under the Authentication area -- there may have been a hiccup during a patch or installation. You can resolve by trying to Modify the install, adding the database types, then repeating the Modify, and de-selecting them.

Permissions Problems Prevent Database Access

Recently I inherited a database from another programmer (created / stored with SQL Management Studio 2008), and I am having massive difficulties accessing, modifying, or even viewing the previously created databases.
Specifically, when I try to load one of the databases in SQL Management Studio I get the following error message:
"The database [database name] is not
accessible. (Object Explorer)"
I am connecting to the SQL server with windows authentication.
Anyway, is this a permissions issue left over from the last dev? (he's unavailable, unfortunately) And is there an easy work-around short of completely reinstalling SQL Management Studio?
Edit: Update:
Upon trying to access User Mapping, as suggested below, I got the following error message:
"One or more databases are inaccessible and will not be displayed in list."
Unfortunately, none of the databases I am trying to access appeared in the list, so I assume they are still inaccessible.
It could very well be a permissions problem. If you open Object Explorer in SQL Server Management Studio and expand the Security node (the one under the server instance, not the Security tab under the individual databases) and then expand the Logins node you'll see the list of logins that have been created on the server. Have a look at the properties of each of those and check out the User Mapping information. You'll be able to see which logins are mapped to which databases. It's possible the previous programmer only granted access to the database to certain logins. If you find a login that's mapped to the database you want, try changing the password of the login and then connecting to the database with that login and password. NOTE: be careful when changing the password as it may affect production applications that are using that login and password!
This message:
"One or more databases are inaccessible and will not be displayed in list."
Means that the user you are using right now cannot access to that db. If you can enter with a user that does have access and from that user change your actual user's rights through User Mapping, then you will see it.
You need a dba (or someone with dba equivalent access) to give you rights to the database.

Access Log in troubles

Lately there has been a problem running some of our reports in access. Last week(the beginning of the week) we tried to run a reports lets call it A and it kept giving us the log in prompt. Even when the correct user-name and password were entered the log in box would just keep reappearing until cancel was pressed.
I clicked the debug and checked the query. I then logged into the database it is pulling the data from with the same user-name and password and received no trouble. Around Wednesday A was working again, even though nothing was changed. This week A is working but another report B is doing the same thing..
Anyone have any idea what this could be? I'm thinking maybe someone else has the report open? Any help is appreciated.
EDIT: I have narrowed down the error to one linked table that is causing the login prompt. It seems it has the DSN setup but no database specified. So i just need to relink the table..Is there anyway to do this at the GUI level? Also should I leave this question up for future users or just delete it?
Was the login prompt from Access or from Windows? If from Windows, then I'd say that there was some sort of file permission or network access issue at hand. If from Access, then I would say that something in the SYSTEM.MDW that you are using is corrupt or has been reconfigured.
If the login prompt is from ODBC it probably means that the credentials that are being used to access the backend database (per your comments you mentioned it was SQL Server) are either invalid or disabled. (Or it could be as simple as the backend database is/was temporarily unavailable).
If you are using linked tables in Access to a SQL Server it means that an ODBC connection was created and you might try verifying that the ODBC connection is working ( Control Panel, Administrative Tools, Data Sources(ODBC) ). In that dialog there is a place to test the connection.