I have a SSRS report in AX 2012 with a parameter, where Values is set to "Unbound Values" (Non-queried). In the popup for adding values, I have added a couple of lines with a value and a label like the following:
Value: MainAccountId,
Label: =Labels!#SYS135766
But when I preview (or run the report from AX after deploying), the text "Labels!#SYS135766" is shown as label in the dropdown on the dialog (instead of "Main account").
I have also tried with "Labels!#SYS135766" and "#SYS135766", but with no luck.
Does anyone know how to get the label ID translated to a text using unbound parameter values?
I know this is an old question, but still posting the possible answer hoping that it can help.
Cite from a post by Namukoa Isaac:
Reasons for the problem:
You have moved your AX service account from AX domain account from AX domain admin group
You have changed your SSRS service account password.
Solutions:
From the Start menu, point to All Programs, click the SQL Server folder, click theConfiguration Tools folder, and then click Reporting Services Configuration Manager.
In Reporting Services Configuration Manager click Connect and then click Service Account.
Set the password and then click Apply. The account and password should be the same as the Microsoft Dynamics AX proxy account.
System will ask you to backup your encrytion key, and then will some settings on the backhand.
Now Click the ServerName/MSSQLSERVER on the left top of the reporting server and then click Stop. Then click Start to restart the server. Always check with the SQL administrator and make sure no other users are connected to the server before you restart the server.
Related
I know there's an earlier question with this subject here, but the OP never reported if the one answer resolved the issue. And since
Internal Server Error
is about as user-unfriendly as you can get, I would love to change this to something that feels more like "a message" than "an anvil dropped on your foot".
I have found one other SO post that tangentially relates to this issue (about that disappearing "duplicate emails" switch), but the problem is indeed not about whether or not to allow duplicate emails (or how to revive hidden admin controls) but how a very ordinary issue is communicated to the user - well, like how Keycloak notifies the user when they try and register with an existing username.
We're currently using the Docker version of Keycloak 12.0.4 with some customisations (a custom BCrypt module, some logging changes) running in IBM Cloud, using a Postgresql DB. We also added a custom theme & internationalisation. The same error occurs also when using the default Keycloak theme, though.
Here are our Login settings:
It turned out to be a configuration issue, but so deeply hidden that even the Keycloak developer who looked into the ticket I created had glossed over it.
The perpetrator was in menu Configure > Authentication > tab: Flows > choose dropdown: Registration > Profile validation radio button [o REQUIRED | o DISABLED]
This was set to disabled, which in effect prevents the duplicate email check in the registration form that the Realm settings > tab: Login form suggest are active. But then, of course, the database won't like that, with above-mentioned result.
This combination of settings should at least issue a warning, of course. I hope this will be corrected.
I have an xrdp setup on my raspberry pi.
XRDP:
I only have one session in the list (PI).
Is it possible to skip this screen and go directly to the remote control after connecting?
Thanks
For anyone dealing with this, I'd try saving the configuration on your RDP client. For Windows RDP go to "Options" on the bottom left, and then under "General" enter your specifications. In this case, leave the username and password blank and make sure to save it. From then on those credentials will be used to auto login.
For other clients like Royal TS, right-click on the connection and open the "Properties" dialog. Going to "Credentials" located on the left navigation bar will allow you to save any log in configurations you want to use.
I've never tried this without a username and password, so if it doesn't work with blank configurations, I'd consider setting up a username and password if you want to bypass this page.
In our installer we have multiple form components in which we hide some inner options in case the user have choose a specific option.
For example: In this screen - this is the default displayed options.
If the user choose different Authentication than the default SQL Server Authentication (Windows Authentication), than the installer hides the User Name & Password fields.
The problem happens while on upgrade. If the user previously choose the Windows Authentication option - the displayed screen will be like this:
It's not good, because while connecting with Windows Authentication the user input User Name & Password shouldn't be presented.
The Authentication input is defined as Combo-Box & have the Selection change script property like this:
if (selectedItem.equals("Windows Authentication")) {
((JTextField)formEnvironment.getFormComponentById("1418").getConfigurationObject()).setText("");
}
formEnvironment.getFormComponentById("1418").setVisible(!selectedItem.equals("Windows Authentication"));
formEnvironment.getFormComponentById("1677").setVisible(!selectedItem.equals("Windows Authentication"));
Basically I do understand why it won't work on upgrade - since it work by selection trigger, it won't be applied by default by the installer.
Is there any way applying this logic also upon upgrade?
You have to execute the same logic in the "Visibility script" properties of the "User name" and "Password" form components. You don't have the "selectedItem" parameter there, but you can query the variable that is bound to the "Authentication" form component, i.e. context.getVariable("variableName").
I'm trying to start SQL Server Express from command line using the following command:
net start MSSQL$SQLEXPRESS
But I get this error:
System error 5 has occurred.
Access is denied.
I have administrator privilege and my OS is Windows 7.
Thanks to #SamiKuhmonen my problem was solved.
I created batch file (named start sqlserver.bat) conatins the following command:
net start MSSQL$SQLEXPRESS
I created a shortcut to my batch file.
And run it as administrator like in this
screenshot
Run Registry Editor (RegEdit).
Navigate to HKEY_LOCAL_MACHINE.
Right click on HKEY_LOCAL_MACHINE, and select Permissions .
Click on the Advanced button.
In “Advanced Security Settings” dialog window, go to the Owner tab.
Select and highlight the currently logged on user name or Administrators group (if user is a member of Administrators” in the Change owner to: box.
Select the tick the check box for Replace owner on subcontainers and objects option, and click OK.
Back in “Permissions” dialog window, click on Add… button.
Enter everyone in the Enter the object names to select text box, and click on the Check Names button.
Hope it helps!!!
If there is error with the user ID entered, correct the error. If there is no error found, click the OK button.
Back in “Permissions” dialog window, select and highlight the newly added user name in Group or user names: section, and tick the checkbox for Allow access right next to Full Control in the Permissions for Everyone section.
simply create the batch file as eg.bat
and it's content as :start ssms
I am unable to solve an issue with a report on SSRS.
The scenario is : a link in a Silverlight application loads a new web page containing a Microsoft.Reporting.WebForms.ReportViewer control. The parameters for the control are passed in the QueryString to the new page.
If the date is passed as 01/08/2011, when the report is loaded, the date control on the report viewer has the value 08/01/2011 (i.e. it has been converted to American format and my locale is United Kingdom, en-GB).
This only happens in the deployed solution, it works correctly in Visual Studio on my local PC. My IE settings are correct.
I made the following checks on the deployed IIS Server (IIS 6.0):-
The security account for the relevant Application Pool = Network Service.
In the Registry the SID for this user is S-1-5-20 so I checked the registry settings under HKEY_USERS > S-1-5-20 > Control Panel > International . These were all correctly set for United Kingdom. Although theoretically they should not have an effect I also checked the same settings for Local System (S-1-5-18) and NT-Authority (S-1-5-19) which were identical.
I next checked the Culture and UI Culture on the web site. These were as follows: -
Right-click website - Properties > ASP.NET.
Click the 'Edit Global Configuration' button to check the server config settings.
Select the Application tab and view the values for Culture and UI Culture.
Both values are set as en-GB. So OK.
Did the same in the 'Edit Configuration' button which is for viewing/editing the specific application's config file.The websites' config file values will supercede the server config file values. These are also OK.
Next I checked the SSRS Server.
Service runs under 'Local System' account.
Registry settings for this account are correct HKEY_USERS > S-1-5-18 > Control Panel > International.
S-1-5-19 and S-1-5-20 also correct
ReportServer.aspx page directive includes Culture="en-GB"
(e.g. <%# Page Language="C#" AutoEventWireup="true" Inherits="Microsoft.ReportingServices.WebServer.ReportViewerPage" Culture="en-GB"%>)
In code the parameter values are set using Microsoft.Reporting.WebForms.ReportViewer.SetParameters(ms.ReportParameter []) and ms.ReportParameter(name, value, visible) and the parameters are definitely the correct value when they are received at this point by the web app (when I step through in code).
I don't know where to turn next. The one difference I have but I can't imagine it is the problem is that the querystring is URLEncoded on the deployed version but not in the design on my local PC i.e
[server version]
...%26END_DATE%3d31%2f07%2f2012+00%3a00%3a00%26START_DATE%3d01%2f08%2f2011+00%3a00%3a00
[local version]
...&END_DATE=31/07/2012+00:00:00&START_DATE=01/08/2011+00:00:00
I would be extremely GRATEFUL for any suggestions that anyone has.
If you pass in the date in dd-mmm-yyyy format then it is unabiguous, eg 18-Jan-2011.