A micro-services architecture based solution developed in .NET Core 3.1 / EF Core 3.1 / OpenIddict 2.1, works fine in development environment.
But in the client environment (Windows Server 2012 R2, with Server Hardening), Identity micro service couldn't able to connect to the SQL Server 2014 database server, and LINQ code which fetches data from the database does not throw any exception.
Startup.cs, database connection code
services.AddDbContext<IdentityDbContext>(options =>
{
options.UseSqlServer(Configuration.GetConnectionString("DefaultConnection"));
options.UseOpenIddict();
});
Using a sample console app (developed in .NET Core 3.1 / EF Core 3.1) able to connect to the client database, this is to verify whether server hardening causes any problem on Windows Server 2012 R2/.NET Core 3.1/EF Core 3.1.
What is causing the database connect problem in Identity micro services? Any help would be greatly appreciated, thanks.
Basically, a named instance caused the problem, had to uninstall and reinstall the named instance.
Related
Im trying to dokerize my .NET Web API application that is connected to an SQL Server database in order to be able to deploy it on Digital Ocean.
Since DigitalOcean does not support .NET applications, I need to dockerize it in order to deploy it there. The app itself is connected to a SQL Server Database and when I dockerize it I cannot access the database. The database uses "Windows Authentication" in SQL Server and it seems that because of this, it is harder to dockerize and conncect (through containers) the .NET application to the database.
My question is:
Is it necessary to make this connection and dockerize both the .NET application and the SQL Server Database or is this something that is not required to deploy the application since the database will have to be migrated to DigitalOcean.
I'm looking for someone that is familiar with DigitalOcean and knows about application deployment there.
Thank you!
I deployed a solution built in ASP.NET MVC 5 with C# and SQL Server as database to Server "X" with a locally installed SQL Server.
I moved this already deployed to a new server "Y" through "FTP" where SQL Server is not locally installed.
Both server have the same Windows OS and IIS versions.
I am getting the following error when I try to browse the deployed solution in server "Y".
I am unable to make out the reason.
I have these questions:
does an ASP.NET MVC 5 solution with database require local SQL Server DLLs? If yes, what are those?
Just FTP of deployed solution is not enough for moving the solution to a new server?
Does the solution need to be redeployed to new server using Web Deploy feature?
Error 193 is referring about 32 bit vs. 64 bit conflicts.
How can I resolve this?
Is there a way to use the Snapshot Debugger against Azure AppService WebJobs?
I know it works with AppService HTTP applications but I would also like to use it with .NET executables running as Azure App Service WebJobs.
It really has the default supported scope:
https://learn.microsoft.com/en-us/azure/application-insights/app-insights-snapshot-debugger
Snapshot collection is available for:
.NET Framework and ASP.NET applications running .NET Framework 4.5 or
later.
.NET Core 2.0 and ASP.NET Core 2.0 applications running on Windows.
The following environments are supported:
Azure App Service.
Azure Cloud Service running OS family 4 or later.
Azure Service Fabric services running on Windows Server 2012 R2 or
later.
Azure Virtual Machines running Windows Server 2012 R2 or later.
On-premise virtual or physical machines running Windows Server 2012 R2
or later.
So it was not in above list, I suggest you submit a feature request to the product team:
http://visualstudio.uservoice.com/forums/121579-visual-studio
I have 2 applications, one is written in vb6 and the other is asp.net web application.
from both of them I'd like to connect a remote (but on the same network) sql server 2008 r2 database.
Somehow, this doesn't work. I wanna put the asp.net application aside for now and just test the vb6 one.
The strange things is, if i install sql management studio on the same machine where
my vb6 application is installed and try to connect my remote sql server using windows authontication it works.
Thanks in advanced.
A shot in the dark: 2008R2 is much newer than vb6. What type of data connectivity are you using in the vb6 app?
I just changed a simple SQL Server Express Datebase to SQL Server CE 4. This DB lives in the App_Data folder of an ASP.NET WebProject, which is also the host for my Silverlight project.
Then I build a EF-model based on this SSCE Database using Entity Framework 4.
And this model is the base for my WCF RIA Service.
Everything compiles and runs locally without problems. But I get an exception when trying to compile on our build server:
C:\Program Files (x86)\MSBuild\Microsoft\Silverlight\v5.0\Microsoft.Ria.Client.targets (305): Schema specified is not valid. Errors: MyModel.ssdl(2,91) : error 0175: The specified store provider cannot be found in the configuration, or is not valid.
From the log file it seems, that the exception happens in the Silverlight project - not in the Webproject.
Does anybody know what I am missing?
Thanks!
Is SQL Server Compact 4.0 runtime installed on the build server?