I'm using NServiceBus in my application, and since NServiceBus 5 RavenDb is not the default persistence and is not installed with NServiceBus. So I downloaded RavenDB-Build-2952 and installed with Development option on setup.
When I tried running my project (which still uses NServiceBus 4) I got an error that the license for RavenDb is not valid for windows authentication. There are not special configuration in my NServiceBus code regarding persistence of RavenDb.
How can I make sure that RaveDb installation uses the NServiceBus license?
Are you sure this is an error, and not a warning?
I had this problem a few months ago, and even though this message appeared in the log, the system functioned without issue.
Try ignoring the error/warning (I'm assuming you're debugging), and see if persistence still functions as needed?
Related
I have .net framework 4.8 web site deployed on IIS 10. And It's pool stops on every first request after each start.
Here is the list of programs and features on server:
Programs and features
In Application Windows log I found 10 errors per each request. Everyone error is:
The Module DLL C:\Windows\system32\inetsrv\aspnetcore.dll failed to
load. The data is the error.
And in System log I have warning:
A listener channel for protocol 'http' in worker process '2968' serving application pool '{MyPoolName}' reported a listener channel failure. The data field contains the error number.
With binary data in details tab: In Words 0000: 8007007E
I tried to repair installed version of .net 5. Also tried to install .net framework 4.8, but installer didn't allow to do it because of:
.NET Framework 4.8 or a later update is already installed on this
computer.
I even tried to create site with empty directory. When I create one on my computer it shows "403.14 — Forbidden" as it should. But after doing the same on server empty site pool stops as my site's pool.
Have you ever faced such a problem? I have no idea how to fix it!
I have .net framework 4.8 web site deployed on IIS 10. And my IIS pool stopped on first request. Researching similair issues I found this artcle on the Microsoft Monitoring Agent APM service. This service was disabled, I removed the Microsoft Monitoring Agent APM as it was not being used. My application now successfully launches.
https://kevingreeneitblog.blogspot.com/2017/03/scom-2016-agent-crashing-legacy-iis.html
Thank you for your help. I solve the problem with complete reinstallation of server OS and components. My consider is that the problem was into iis or OS component.
Lately I started noticing ".NET Runtime version 4.0.30319.0 - There was a failure initializing profiling API attach infrastructure. This process will not allow a profiler to attach. HRESULT: 0x80004005. Process ID (decimal): 10288. Message ID: [0x2509]." on our production Windows Server R2.
This server is mainly used for IIS hosted WCF service. I googled about the error and found multiple solutions and I tried below.
1) Verified .NET framework with Microsoft's utility and no issues found. That means one of the application is firing this .NET error.
2) Tried tracking process id, but everytime error message has different process id. And I cannot find the pid from all available pid. My assumption is, it recycles the process after error and assign new pid.
What is the best technique to find source of this error? Is there anyway I can get pid history logs?
I checked all the recently installed softwares and uninstalled the ones which was installed after the first error date.
For me, it was Wireshark, after uninstalling I do not see this error anymore.
Cheers!
I'm liking a lot what I see about Service Stack, and want to use it with Azure. I found the following project and it compiles ok, but there is either something not mentioned in the readme documents or the 2.1 vs. 2.0 version of the Azure Emulation services is not compatible (which seems unlikely)
I probably have to setup the store manually, but I don't see any interfaces in the emulator to do that.
https://github.com/letsbootstrap/Razor.ServiceStack-On-Azure
Message=Login failed for user 'RazorServiceStack'.
What is the impact on existing code to migrate from WebSphere MQ V6 to V7?
Can we make simply the change?
Like all good questions, the answer here is "it depends."
First of all, don't go to v7.0, go to V7.1 at least, better yet to V7.5.
Using client or bindings mode connections? You can upgrade the QMgr without touching a client-based app in most cases. Any version of WMQ client can talk to any version of WMQ server, however its best not to leave apps on an unsupported version of WMQ client. Of course, the app running on the old client won't get the new function such as automatic reconnect or performance improvements, even though the QMgr is at V7.5.
Using SSL? The SSLPEER element order changed and the commands to manage certificates changed. Good news, cert management is now performed with runmq*km commands living in the {mq install}/bin directory so you don't need to hunt down the GSKit directory and figure out whether to use gsk6*, gsk7* or gsk8* commands.
If you go from 32 to 64 bit, you may need to recompile programs or exits.
Correct settings for PATH, CLASSPATH and LIBPATH change across versions.
There's much more and it's well covered in the Infoceenter. Each Infocenter has a section on migration. Within that section, there's subsections by version and within those there are subsections by platform. Pick the target version of WMQ (that's V7.5, right? Say yes!) and and drill down. Start here:
Migration from V6.0 to V7.5
Migration from V6.0 to V7.1
Migration from V6.0 to V7.0
There is NServiceBus handler run on .net 4.0. I need to start it from VS 2008 project with 3.5 runtime (more specifically from SSIS 2008). The message to be send to the handler is parameter-less. What I tried:
I can not use NServiceBus API because of different .net versions, just can not add reference to the newer runtime library.
My other idea was to use NServicebus Gateway, but it turned out to be too difficult to run (xml+jsonp+get protocol with bunch of params) and lack of documentation.
Then I tried to send MSMQ message, but it did not work as well, because NServiceBus requires it to has special caption and extension message area which I can not specify, and it would be not reliable enough even if I could.
Are any other ideas on how to run simple parameter-less handler?
You can use the 2.6 version of NServiceBus which supports .net 3.5 - available here: http://www.nservicebus.com/Downloads.aspx