Why Modification Indices CheckBox unable to check? - amos

I want to do a 2 order CFA with AMOS. My data set does not contain any missing values. When I try to run the model, it says "The model is probably unidentified....".
So I tried to increase the modification level by checking the modification indices checkbox.
After I checked it and run again, it gives me the following error.
Error ScreenShot:
Can anyone help me with this?

Related

How to remove Routine Group error from workbench?

I'm using MySQL Workbench and I am trying to create a routine. However, At the time of creating routine some error comes,then i deleted that routine. Now I synchronize the model with the existing database, the Routine group error is coming, though i remove that routine group. Can anyone help me how to remove this error from Model?
The _SYNTAX_ERROR suffix is added by MySQL Workbench to indicate that it found a syntax error in your routine code. Once you fixed that the name will change back to what you gave it. And then you can also synchronize your model.
I faced the same issue, cause i copy&pasted some c# code into a routine group, and it immediately became invisible by workbench. Synchronization now always reporte errors, even after deleting the whole routine group. The faulty code was stuck somewhere, inaccessible through the Workbench UI.
Just found a solution atm:
Do a regular synchronization and tell Workbench to change the sync-direction on the error entries. This will remove the faulty lines of code, even if they are not accessible through the Workbench UI.

Using "Save start values in the model" option to help the convergence in Dymola

I build a model in dymola. Even though there are some errors during the initialization process, but the calculation succeeded at last.
After the model converged successfully, I tried to use the "Save start values in the model" option to get the right iteration variable strat values stored into the model so that the model would NOT get errors in the next calculation. But after I did this and tried to do calculation once more, I still got the same errors.
So, my question is:
Could I use the "Save start values in the model" to help convergence?
If so, how should I do it?
Are you certain that there are error messages?
The simulation log indicates that you have enabled
Simulation Setup>Debug>Nonlinear iterations
That gives debug messages in the simulation log for every iteration of the non-linear solver, regardless of whether there is a problem or not. (Which can be good for analyzing errors, but should not be on as default as it generates large log-file.)
If disabling that flag doesn't remove all messages, it would be necessary to see the remaining messages and the model to understand the problem; as the previously indicated procedures should work.
The reason is I set the fixed attribute of some parameter as false, the fixed attribute of some variable as true, so I could use the variable's value to initialize the system, and the corresponding parameter would be calculated. when using "save start values in the model" option, it would store the result into the parameter's start attribute, but its value attribute would keep unchanged. When I do simulation again, Dymola would NOT use the parameter's start attribute, it would still use the parameter's value attribute. After I change the value attribute manually, there would be no error anymore.

Cached plan must not change result type

Our service team is getting the error Cached plan must not change result type sometimes when I modify the length of a column or add a new column in the table.
I tried solutions mentioned on Stack Overflow like Postgres: "ERROR: cached plan must not change result type"
I have tried autosave=conservative to resolve this issue but still, I am able to reproduce this issue. I used below JDBC connection string
jdbc-url: jdbc:postgresql://172.16.244.10:5432/testdb?autosave=conservative
why is this property not working in my case?
Also, I tested with prepareThreshold=0 and its working fine. But I think it will impact performance because it will never use client-side prepared statements.
I just want to know the best solution to avoid this error.

Data for some bound fields not appearing on report

I'm creating a 'SectionReport' (Active Reports V.9), and am dragging bound fields from the 'Report Explorer' directly onto the report. I've written the SQL query, which executes and returns the correct results as expected.
However, only a small portion of the bound fields are displaying data from the table.
Again, when I execute this in the 'Query Designer', I see all data. When I save that exact query, only some of the data is populated on the report.
This process seems so straight forward and yet I seem to be missing something.
Please help and thanks in advance!
So you're saying the data is returned but not showing up in some of the fields? Have you checked the binding for each of those fields?
Can you step with the debugger and verify that in the detail_format even there is data in report.fields for those records that have missing values.
can you add debug statements that print each field value in the detail_format event.
based on what you described all I can offer is some diagnostics techniques. If you'd like please send your report to our support team and we can properly inspect it and help you out http://arhelp.grapecity.com/
If you are using the enduserdesigner sample or the pre-compiled exe that comes with the installer, can you please make sure that the PreviewPages to a larger number instead of 10.
You can change the value by follwing these steps. in report exploer, double click the settings node. go to gloabal settings tab and change the previewpages value.
If this is not the case, please attach the report. There are no other settings that will cause this.

Unable To Change Preview Setting In Eclipse BIRT Report Designer

I've just begun using the BIRT report designer for Eclipse to create reports from data in a MySQL database. When attempting to preview the result set from a created data set, I receive the following error:
SQL error #1:You have an error in your SQL syntax; check the manual
that corresponds to your MySQL server version for the right syntax to
use near 'OPTION SQL_SELECT_LIMIT=500' at line 1
I understand that this syntax is invalid with MySQL, as it should be
SET SQL_SELECT_LIMIT=500
However, I cannot figure out if/where I can make this correction, as it is added automatically by the report builder when generating the preview.
Furthermore, in the IDE preferences, I have selected the 'No Limits of number of rows to display' option, trying to bypass this statement altogether, but continue to receive the same error, indicating that it still is trying to preview 500 or less rows, even after deleting the first data set definition and remaking it after the option was changed and restarting Eclipse.
If anyone has any suggestions for either changing the syntax or getting the No Limits option to work correctly, I would greatly appreciate it.
Was actually able to figure out the issue with getting the correct syntax thanks to this SO post regarding Netbeans. The MySQL JDBC driver simply needed to be updated. Preview no longer generates depreciated syntax.