I just checked the latest source out of our repository after the installer (NSIS if it really matters) was created and a bug was discovered.
I started receiving the runtime exception CoCreateInstanceEx: The specified service does not exist as an installed service. on the following code:
Opc.IDiscovery discovery = new OpcCom.ServerEnumerator();
Opc.Server[] servers = discovery.GetAvailableServers(Opc.Specification.COM_DA_20);
Previous to creating the installer it seemed to work fine and this particular snippet of code hasn't been touched in weeks.
According to a quick search on the exception description, this probably has something to do with system drivers. But nothing has changed on the hardware (virtualized development system) and nothing has been installed since the check in where this code worked.
Any ideas on what caused this to break, and how do I fix this?
Hardware? This sounds like a COM DLL got unregistered - figure out what COM object is attempting to be instantiated and run regsvc32 on it.
Related
Using Visual Studio 2013, when try to deploy the Report, the session Crash
I attach the messages
Do you have any idea to solve this issue?
by Event Viewer
I already followed this way - BUT the issue has not been resolved.
http://www.wkcerp.com/ax/crash-or-hang-during-ax-project-or-report-build-visual-studio-2013-ax-r3-cu8/
Thanks
I had the same issue here, and in my case the problem was a faulty installation of the SQL ADMd.Net components. Try and reinstall those.
There is a DLL, named Microsoft.AnalysisServices.AdmomdClient.dll, which could not be found in my case. This caused a stackoverflow exception in my case. The admin reinstalled those components, and the DLL got installed, too. Deploying reports is now possible :).
I figured this out by attaching one VS instance with debugging enabled to another VS instance, with which I tried to deploy reports.
Also, I had to enable debugging for .NET Code in the settings.
I set a breakpoint at the function
Mscorlib.dll!System.Runtime.TypeHandle.GetTypeByName
And that's where I noticed, that the same block functions were called over and over, trying to load the DLL, but not being able to find it. It is the nLoad function.
(https://referencesource.microsoft.com/#mscorlib/system/reflection/assembly.cs,460c8abec12d58cd).
This eventally caused the Exception, and the exception code 0xc00000fd, which is a Stackoverflow exception.
I can't post images here, but I hope it's still understandable.
Best regards,
Jannik.
I created a new application with react native windows, and it works well the first (few) times I run it, however, when closing the application I always end up with the following warning:
Attempt by security transparent method 'System.Reactive.Concurrency.CoreDispatcherScheduler..ctor(Windows.UI.Core.CoreDispatcher)' to access security-critical type 'Windows.UI.Core.CoreDispatcher' failed.
I've tried this on more than one computer and all of them get the same error but I can't find a way to fix this, meaning I cant proceed with my Native project in fear that it will malfunction every day.
How do I fix this, to stop this from happening again, or is it a bug?
I'm a novice in React Native myself, but here are a few suggestions:
1) There's an issue logged in GitHub on this exact problem: https://github.com/Microsoft/react-native-windows/issues/1954
2) I personally find that I get this with command-line execution (react-native run-windows) but I don't think(?) that I've seen it when running from inside Visual Studio. Try that approach to running instead.
3) As described at GitHub - I've found that deleting windows\Debug folder before running tends to resolve the issue.
I have these CLR types installed on my local https://puu.sh/yEWG5/b4f77fba7b.png
Also, I have SQL server 2016 installed on my local system but when I try to run the project I get error as below
https://puu.sh/yEWQm/78a4220830.png
Can someone help? I tried installing latest nugget package from https://www.nuget.org/packages/Microsoft.SqlServer.Types/ but it did not help.
Though I am able to add a column of type geography in a table in my local database. It fails at runtime when I run my project and error comes as below
https://puu.sh/yEWQm/78a4220830.png
According to the docs if you have installed the CLR Types it should load from the GAC so I'm not sure why that didn't work for you. (I would check that you have the correct version as your dependency)
However, we do use the SQLServerTypes in our app without installing the CLR types by using the following method (this method is described in the readme.htm that comes with SqlServerTypes).
Grab the SqlServerTypes.nupkg and extract it to a folder lets call this folder SST from now on.
(Locations of the files I talk about in the following steps may differ from version to version but, the principle is the same)
Create a SqlServerTypes folder in your project
Copy the SST/nativebinaries/x86 and x64 folders into your new SqlServerTypes folder
Also copy the files from SST/content (you should see Loader.cs and readme.htm) into the SqlServerTypes folder.
Now all you need to do is call the Loader when your app boots up.
We do this during our autofac setup by making this call.
Utilities.LoadNativeAssemblies(AppDomain.CurrentDomain.BaseDirectory)
You may need to adjust the param passed into this method to work with your application. If the correct path is used you should have access to the spatial types in your code.
edit: It may be possible to just call the LoadNativeAssemblies straight away (and avoid all the work I posted above) if you have installed the nuget package in your app but, I have not tested this as we are stuck on an old version of SqlServerTypes.
Because i cannot put a comment i have to put a answer, you can check that, that article and this, this, this and this answers, i hope they guide you to someting usefull.
i am getting this error when try to create new web service client.
IWAB0503E Unable to update Java build path. Please check your system environment.
Some web searching uncovered that what this error really means is “The Web Services generation tool detected multiple versions of the javax.xml.soap plug-in installed. Resolve this error by removing the conflicting plug-in.”
Sure enough, when I checked in Eclipse there were two versions.
WebService
I encountered two speed bumps when testing this theory:
There’s no easy way to uninstall a plug-in within the Eclipse UI, so I had to resort to removing the directory from eclipse\plugins directly from Windows Explorer.
Which version should I remove? It took me two tries to figure out which version was causing the error. Turns out that newer is not always better…in this case 1.3 was at fault and 1.2 (javax.xml.soap_1.2.0.v200905122109) was the version to keep.
This is old but, in my case the details of the error were:
IWAB0503E Unable to update Java build path. Please check your system environment.
java.io.FileNotFoundException: /lib/saaj.jar
So \lib\saaj.jar was not found in folder
C:\sts-4.8.0\sts-4.8.0.RELEASE\plugins\javax.xml.soap_1.3.0.v201105210645\
I created the folder lib and copied saaj.jar in it from another STS instance that I had and then it worked.
I have a WP7 project in VS2010 pro/ultimate and I have added a web reference from another project on the same solution. The web service project is just a normal website project, I just created .ASMX file. I tested the service using web browser and it works fine.
The problem is, after I added this service as service reference, I cannot reference it in my WP7 project and I can't view it in Object Browser either as if it doesn't exist.
I use local URL like 'http://localhost:12345/WebService.asmx' when I added the service, VS can see all the methods and can add successfully. Very strange for me and I don't know how to solve this issue.
Anyone can give me any clue on this? Thanks very much.
I've had a similar issues before- on one machine, a restart was required, on another, I had to uninstall ALL of my SL stuff, then uninstall Vstudio, then reinstall and reapply any SL add-ons.
Then it worked fine.
Also had a friend with the same issue- uninstall all, then reinstall worked for him also.
I believe these were machines with pre-rtm SL and Phone bits on them.
I've had a similar problem. I created a WP7 project using VB.Net. I built a WCF Class web service, a client side proxy class, and then a WP7 application with the service reference. When I added the service reference, the code generating utility would not build the required Reference.svcmap file detail (it only created the header information). However the project would still compile, yet I couldn't reference the service in code as it didn't exist in the underlying files.
I tried recreating the WP7 project in C# and everything worked. My guess is that the VB implementation of WP7 might still have some issues, however that is a guess only. I'm keen to see if anyone else has had the same issue specific to the VB WP7 template or if it is something else.
I bumped into the same problem, but it was fixed after a reboot as suggested in this thread by dethSwatch.
I do remember that a silverlight SDK update was installed a bit earlier, maybe the reboot is required after the update?
I think this issue might be related to the January Update to the WP7 tools. I managed to fix this issue by installing the VS10-KB2486994-x86.exe fix found on the above page. That sorted the issue I had with generating a client side proxy for the WCF service I wanted to call. Hope this helps.