Error when migrating efcore to version 3.1 - entity-framework

I am getting error when migrating to efcore3.1
This line of code shows error :
entity.HasOne(d => d.ContentControl)
.WithMany(p => p.Content)
.HasForeignKey(d => d.ContentControlId)
.OnDelete(DeleteBehavior.ClientSetNull)
.HasConstraintName("FK_Content_ContentControl");
Error :
Error CS7069 Reference to type 'ReferenceOwnershipBuilder<,>' claims it is defined in 'Microsoft.EntityFrameworkCore', but it could not be found
how can i solve this?

Probably missed to upgrade the dependent packges like Microsoft.EntityFrameworkCore.SQLServer. Check that.

Related

jboss duplicate resource [(\"core-service\" => \"vault\")]"

So, my question is in theme.
Firstly, I added into EAP 6 my vault with command
/core-service=vault:add(vault-options=[("KEYSTORE_URL" => "PATH_TO_KEYSTORE"), ("KEYSTORE_PASSWORD" => "MASKED_PASSWORD"), ("KEYSTORE_ALIAS" => "ALIAS"), ("SALT" => "SALT"),("ITERATION_COUNT" => "ITERATION_COUNT"), ("ENC_FILE_DIR" => "ENC_FILE_DIR")])
But I got mistake and try do the same command with correct fields, but get exception
{"outcome" => "failed",
"failure-description" => "JBAS014803: Duplicate resource [(\"core-service\" => \"vault\")]",
"rolled-back" => true
}
In standalone.xml I deleted any vault but still got that error.
How to fix it?
Or How can I find that in my web-console?
The problem was because I had to stop JBoss and after that remove
<vault>...</vault>
elements from standalone.xml.
After that start JBoss and again do action from management cli. There is noone error happen

Circular reference detected on TYPO3 11 backend login page

I have a weird error when trying to call the TYPO3 11 backend login page.
I updated from TYPO3 10 and can't login anymore.
I already removed all of my custom extensions, but the error persists and I can't make out where it comes from or why.
It seems to crash when reaching the first f:form.hidden field of the default login Fluid template.
As this is an obvious issue that probably would have got caught by core devs, I am pretty sure that this is correlated to a configuration of my instance, but as I said, this is to weird of an issue for me and I have no idea where to dig for the issue.
This is error message:
I can provide the whole stacktrace if needed.
Did you update your .htaccess file with the new rules for the TYPO3 backend? You can find a sample file in the the Resources folder of install tool extension: typo3/sysext/install/Resources/Private/FolderStructureTemplateFiles/root-htaccess
And I assume that you cleared all caches in the install tool and did a composer dump-autoload.
I discovered the source of this issue.
I had the following configuration automatically generated in my LocalConfiguration.php.
'SC_OPTIONS' => [
'GLOBAL' => [
'softRefParser' => [
'email' => 'TYPO3\\CMS\\Core\\Database\\SoftReferenceIndex',
'ext_fileref' => 'TYPO3\\CMS\\Core\\Database\\SoftReferenceIndex',
'notify' => 'TYPO3\\CMS\\Core\\Database\\SoftReferenceIndex',
'substitute' => 'TYPO3\\CMS\\Core\\Database\\SoftReferenceIndex',
'typolink' => 'TYPO3\\CMS\\Core\\Database\\SoftReferenceIndex',
'typolink_tag' => 'TYPO3\\CMS\\Core\\Database\\SoftReferenceIndex',
'url' => 'TYPO3\\CMS\\Core\\Database\\SoftReferenceIndex',
],
],
...
This caused the above error message. After removing this part from my configuration, the system lets me login and works flawlessly.

Adding smallrye tracing to Wildfly 23

I'm trying to add microprofile opentracing subsystem to Wildfly23 using thins guide: https://github.com/wildfly/wildfly/blob/main/docs/src/main/asciidoc/_admin-guide/subsystem-configuration/MicroProfile_OpenTracing_SmallRye.adoc
However, the second step fails:
[standalone#localhost:9990 /] /subsystem=microprofile-opentracing-smallrye:add
ERROR [org.jboss.as.cli.CommandContext] {
"outcome" => "failed",
"failure-description" => "WFLYCTL0369: Required capabilities are not available:
org.wildfly.microprofile.config; There are no known registration points which can provide this capability.",
"rolled-back" => true
}
I tried adding microprofile config using this model as a reference: https://docs.wildfly.org/23/wildscribe/subsystem/microprofile-config-smallrye/index.html however i get this error
[standalone#localhost:9990 /] /subsystem=microprofile-config-smallrye:add
ERROR [org.jboss.as.cli.CommandContext] {
"outcome" => "failed",
"failure-description" => "WFLYCTL0030: No resource definition is registered for address [(\"subsystem\" => \"microprofile-config-smallrye\")]",
"rolled-back" => true
}
What am i missing? The doc seems fresh enough, last updated in March on 2021...
You also need to install the extensions "org.wildfly.extension.microprofile.config-smallrye" and "org.wildfly.extension.microprofile.opentracing-smallrye" before adding the subsystems.
Also wildfly provides a standalone-microprofile.xml that can server as example.

SOAP-ERROR: Parsing WSDL: Couldn't load from local file

I have a WSDL file which located in my server, I use this file a lot with SoapClient
$client = new \SoapClient(dirname(__FILE__) . DIRECTORY_SEPARATOR . self::$url, array(
'connection_timeout' => 180,
'verifypeer' => false,
'verifyhost' => false,
'soap_version' => SOAP_1_2,
'stream_context' => stream_context_create(['ssl' => [
'verify_peer' => FALSE,
'verify_peer_name' => FALSE,
'allow_self_signed' => TRUE
]])
));
It works as expected but sometimes it still giving me this error
SOAP-ERROR: Parsing WSDL: Couldn't load from '/var/www/public_html/laravel/app/Classes/orders_internal.wsdl' : failed to load external entity "/var/www/public_html/laravel/app/Classes/orders_internal.wsdl"
And it doesn't get back to work until I reboot the server!
Do you have any idea what am I missing?
Regards
I was having this issue too. I have a flow where I have to make 5 different calls to a soap api (in the same execution).
Only the last call was giving the error:
SOAP-ERROR: Parsing WSDL: Couldn't load from /var/www/html/SomFile.wsdl failed to load external entity.
I realized that just before the last call it was a logic to disable load external entities:
libxml_disable_entity_loader(true);
Make sure there is no logic disabling the ability to load external entities in some part of the code.
It is important to notice that libxml_disable_entity_loader() will be deprecated:
Warning
This function has been DEPRECATED as of PHP 8.0.0. Relying on this function is highly discouraged.

Unable to cast object of type 'Glimpse.Ado.AlternateType.GlimpseDbConnection' to type 'System.Data.SqlClient.SqlConnection'

I am getting an "System.InvalidCastException occurred" exception where I am using the EF 6 asynchronous functionality.
The message is: Unable to cast object of type 'Glimpse.Ado.AlternateType.GlimpseDbConnection' to type 'System.Data.SqlClient.SqlConnection'.
This application was upgraded from MVC4 to MVC5 and is using the .Net Framework 4.5 for the first time.
I am aware this has been raised as an issue before; https://github.com/Glimpse/Glimpse/issues/540 but I tried getting the latest version of Glimpse and I still got the same problem.
I am wondering if I failed to uninstall Glimpse properly, either the latest version or the one I used previously.
The code where the exception happened is;
public static async Task<IList<Company>> GetCompaniesAsync()
{
using (var db = new SherryGreenGroupContext())
{
return await db.Companies
.Include("AddressLines")
.Where(x => x.EndOfBusinessDate == null)
.OrderBy(x => x.CompanyName).ToListAsync();
}
}
The exception is;
System.InvalidCastException occurred
HResult=-2147467262
Message=Unable to cast object of type 'Glimpse.Ado.AlternateType.GlimpseDbConnection' to type 'System.Data.SqlClient.SqlConnection'.
Source=System.Data
StackTrace:
at System.Data.SqlClient.SqlCommand.set_DbConnection(DbConnection value)
InnerException:
You should check you don't have Glimpse EF5 installed. That fixed it for me.
If you dont' then just uninstall all Glimpse packages. Clean your solution and reinstall Glimpse.