I'm getting an exception “System.InvalidOperationException: Hashtable insert failed. Load factor too high.”
My application is developed in VS2010 with 4.0 framework and it is working fine in our development environment (4.0 version ) (for 4.0 framework I'm able to find the hotfix and I've installed it in my development environment). In production environment framework is upgraded to 4.5 version and we often getting the mentioned exception.
Application developed : windws 7 - 32 bit OS / vb.net 4.0
Development environment (hotfix installed) : windows server 2008 - 64 bit / dotnet FW 4.0
Prod Environment : windows server 2008 - 64 bit / dotnet FW 4.5
Kindly help me resolving this issue.
Thanks
The hot fix for 4.5 is available here : kb2803754
And we need to contact the Microsoft support to get the hot fix installation file.
MSDN thread for KB2803754 in .NET 4.5.1 framwork
Related
I got only a short warning during build in VS2010
the helper process was unable to initialize due to an unknown error
We use incredibuild 5.0 on Windows 7 and windows 10 helper machines. The coordinator is running under Win10.
Also on the warning window there was an line about .net framework is not compatible. On every machine 4.0 and 4.6.1 .net framework has installed, so no sense... but somehow the only one helper could assign to build which is running windows 7. Any idea what should I try?
coordinator window
warnings
Windows 10 was release long after IncrediBuild version 5.0
Once Windows 10 was released, a new version of IncrediBuild was which certifies the Win10 OS. Once you'll upgrade to the latest IncrediBuild version (which currently certifies the latest Windows updates), your problem will go away :)
Disclaimer: the writer of this message works at IncrediBuild.
An application developed with VS 2010 and .NET 4, originally and successfully deployed on Vista, after installing on Windows 8.1 has exhibited the following problem (after installing the official MySQL data provider version 5.0.9):
A call to DbProviderFactories.GetFactoryClasses returns all the other providers (ODBC, SQL Server, etc.), but not the MySQL provider.
What could be wrong? Is the version not compatible with 8.1? Does the installer not register it so that DbProviderFactories.GetFactoryClasses can find it? Could there be a 64 vs 32 bit issue?
We have done a proof-of-concept using Gatein 3.5 which runs well with JBoss AS7.
However, JBoss AS7 only has a community edition and we cannot proceed with it. Thus, we have to switch to JBoss 6 enterprise version.
Unfortunately, Gatein doesn't work with JBoss 6. I had raised this issue in JBoss/Gatein community and they stated that Gatein in JBoss 6 is not a good combination.
Please let me know some open source portal container which can run on JBoss 6.
Bipul, I think you misunderstood the recommendation in the forum.
You were proposed to upgrade from 3.4 (With JBoss AS 6) to 3.5 With JBoss AS 7.
If you are looking for a solution with GateIn 3.5 and JBoss Enterprise Application Platform 6, you should know that we will very soon release JBoss Portal Platform 6 that will be exactly this.
You can already download an evaluation version here:
https://access.redhat.com/downloads#eval
Tomorrow (Tuesday), there is an intro to the platform: https://engage.redhat.com/forms/20130212_JBossPP_tipsandtricks?sc_cid=70160000000URk2AAG&offer_id=701600000007O1kAAE
Thomas
I was very hopeful that since SQL Server 2012 SQLCLR supports .NET 4.0 that SQL Server Reporting Services (SSRS) 2012 would support .NET 4.0 custom code assemblies. When attempting to upload an rdl (via the Report Manager or via RSBuild) that references .NET 4.0 assemblies, the Reports Manager throws an error stating
This assembly is built by a runtime newer than the currently loaded
runtime and cannot be loaded. (rsErrorLoadingCodeModule)
Is there something I can configure to get SSRS 2012 to load .NET 4.0 assemblies? Will we be waiting until the next major release of SQL Server before we see .NET 4.0 support for custom assemblies in SSRS?
SSRS 2014 is now released and custom code still does not support the .Net 4.0 Framework.
See prerequisites in the "Hardware and Software Requirements for Installing SQL Server 2014"
(http://msdn.microsoft.com/en-us/library/ms143506(v=sql.120).aspx)
It's very amusing that SQL Server 2014 has just RTM'ed a few days ago and is already considered a "legacy application" by the .Net Framework guys who say:
.NET Framework 3.5 is not included by default in Windows 8 or Windows
Server 2012, but you can download and deploy it for legacy application
compatibility.
... see "Microsoft .NET Framework 3.5 Deployment Considerations"
(http://technet.microsoft.com/en-us/library/dn482066.aspx)
I think the bigger issue is whether the support lifecycle of .Net 3.5 SP1 can actually be tied to the OS'es for which it was a default component. Whatever they say, I can't see Microsoft quitting support on .Net 3.5 as long as SQL Server continues making it a prerequisite in a product they are releasing today. The .Net Framework guys can't be too happy with the lazy SQL guys right now...
Actually, I find that reports using .Net 4.0 assemblies will work fine in VS 2010 (PreviewProcessingService.exe)...
And the reports may also work for you when deploying them to SSRS 2012 SP1 in SharePoint 2013 integrated mode.
Here is the authoritative answer on when/where the .Net 4.0 CLR is supported by SSRS: http://support.microsoft.com/kb/2869522/en-us
For those of us who use SSRS in standalone mode (without SharePoint), we might be stuck on the .Net 2.0 CLR for a while.
I might be wrong and there might be more differences but having compared reports downloaded from reporting services and "identical" ones made in Visual Studio using .Net framework 4.0+ I think the only difference is that puts a ReportParametersLayout section in the xml. If you manually remove this from the xml version of the report file then upload hopefully it will work for you
Does any one know how to connect to MySQL 5.1 with Visual Studio 2010?
I have already tried the MySQL Connector/ODBC route and it got me really nasty results. The table rows were all listed as a view in the views section and nothing at all was listed in the tables or procedures folder.
To get the Entity Frame working with VS2010, I had to do the following:
This only worked with Mysql .net Connector v6.3.1 (alpha). Previous versions ignored VS 2010 (click Development Releases)
I had to rename my Framework\v1.1.4322\CONFIG folder. Otherwise the install will fail. Rename it back when finished
(I've blogged about this here)
Update
6.3.2 is in beta and I can confirm this works. (I didn't need to rename the framework folder)
this seems to solve the issue
UPDATED LINK TO LATEST RELEASE THANKS #Christian Payne
Update: looks like there is already a non-beta!!!!
http://www.mysql.com/downloads/connector/net/
As someone else suggests..
http://dev.mysql.com/downloads/mirror.php?id=382641
..fixes the problem.
I had v6.2.3 installed after I had vs2010 installed and the MySQL driver was not shown in the list of the Database Connect dialog. I wrongly assumed I should use the .NET ODBC drivers instead and it caused all sorts of problems. Although I could easily connect to the DB using codebehind, the server explorer wouldn't connect to the DB.
Luckily after uninstalling 6.2.3 and installing 6.3.0 (from the link above) the MySQL driver was added to VS2010, and I was able to connect to the database and see it in my server explorer.
http://bugs.mysql.com/bug.php?id=45122
I was able to get this to work by doing the following:
My Environment:
Development Box -- Win7 64bit,
VS2010 Pro
Deployment Box -- Win2k8 svr with IIS7
running ASP.NET .Net 2.0/3.0/3.5 sp which is
hosted at DiscountAsp.Net (Note:
DiscountAsp.Net does not provide a
MySQL DB when running on a Win2k8
svr, I'm using a MySQL DB that I connect
to elsewhere on the InterWebs)
Steps I took:
Installed MySql.Data, Version=6.3.6.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d
Ref'd the .Net 2.0 version of the MySQL assembly in my ASP.NET MVC2 Web project set to target .Net 3.5 (the path for the MySQL assemblies I used was C:\Program Files (x86)\MySQL\MySQL Connector Net 6.3.6\Assemblies\v2.0)
I ref'd all 3 of the MySQL assemblies (MySql.Data.dll, MySql.Data.Entity.dll & MySql.Web.dll)
I marked each of those assemblies as "Copy Local=True" in my project (a.k.a bin deployment)
Added a MySQL DB connection string to my Project (using the MySQL provider)
Added an ADO.NET Entity Data Model to my project in VS2010 using the connections string
VS2010 took about 30 secs to chew thru my MySQL DB schema but then provided me with a beautiful GUI interface to tweak my MVC Models
Used the DB Entities in my MVC controllers
Deployed the app to my hosted server at DiscountAsp.Net
It works like a charm :)
Erm... through code? Or do you mean the server explorer add-in? Have you tried the latest (albeit GPL-ed) connector version for .NET from Mysql themselves? Again, it's GPL-ed so be aware of the consequences of using that for your own software.
Microsoft Visual Studio 2010 Beta 2 is busted for DDEX providers. They are auto promoting a VS 2008 assembly from 9.0 to 10.0 and it fails. The failure has to do with the fact that a .NET 2 assembly cannot load a .NET 4 assembly.
This worked in beta 1, so it is something they broke.
I even went back and tried the reference DDEX provider from the SDK. It won't load in VS 2010 beta 2 either. That tells me they have something that needs to be fixed.
When is the next beta?