I'm working with an older webservice and updating it to coincide with our new system. The previous system using SSMS for databases while the new system is using Oracle databases.
The web service is written in VB (potentially VB6) and ran on IIS to a custom built UI. I'm just looking to update it to look for the correct fields and use the correct query for the new Oracle DBs.
The problem I'm running into is that Microsoft has deprecated the Oracle classes, so trying to use classes like OracleCommand and OracleConnection won't work. Instead, we are opting for an Oracle DLL, specifically Oracle.ManagedData.Access but with IIS compiling the VB code on run, it doesn't find the DLL and causes an error.
Any suggestions on how to get a DLL into the ISS compiler at runtime?
The error I am getting is a Compiler Error.
"Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: BC30002: Type 'OracleCommand' is not defined."
Thanks in advance.
Related
I cloned a .NET core web application project from a git repository I haven't worked on in awhile onto a new computer. Although I'm not getting any errors in Visual Studio 2017, when I try to run the program locally I get the error page cited below in the browser.
Does anyone have any suggestions as to where to look for problems or settings I should change?
HTTP Error 502.5 - Process Failure
I fixed the issue. I needed to modify my visual studio install to include .NET Core 1.0-1.1 development tools for web.
I found that the DLL name must not contain a space. For example the dll name is "my own web api.dll" and then you will get the above error message as well.
Check if your target server has got correct version of core hosting bundles installed and correct values in web.config.
https://www.danielcrabtree.com/blog/400/how-to-fix-iis-http-error-502-5-in-asp-net-core
Check if your dll file name contains space in it. If yes, remove all spaces in it via assembly name in your project property of visual studio.
We are migrating a sharepoint farm from a traditional DC to a private cloud.
One of the forms in a site is calling some web services, both the sharepoint site and Web Service application are housed by the same IIS server. Sharepoint site and the Web Services application are having different application pool.
After migrating, one of the forms that is calling some Web Services is throwing an error about: data connection error. Looking at the sharepoint logs, we found that there is http error 500 when hitting the form's URL and that we realized that hitting the WSDL from the browser is throwing the same error too.
The error in WSDL is about: Could not load file or assembly <...> or one of its dependencies. This error is gone if we set the application pool settings to Enable 32 bit = true.
However, the rendering of form is not completed because setting the WSDL application pool to 32 bit is causing to throw a FileNotFoundException with stack trace:
at Microsoft.SharePoint.SPSite..ctor(SPFarm farm, Uri requestUri, Boolean contextSite, SPUserToken userToken)
at Microsoft.SharePoint.SPSite..ctor(String requestUrl) at ...
We are sure that the cause of the problem here is the binary "bitness" because we are able to simulate the above exception and able to resolve in the other forms by just setting back the 32bit option to false in application pool.
We would like to seek anyone's idea on how to resolve the issue. Unfortunately, we only have the DLL of the Web Service, it will take for us a while to get some source codes so we are hoping for some solution that requires no re-compilation. Also, the source code that we are to receive is not guaranteed to produce the same DLL that is deployed to production due to the age of this legacy system turned blackbox.
For more information on the versions of softwares used:
IIS, source: IIS 6; destination: IIS 7.5
Sharepoint: 2007 (yes unfortunately due to alot of reasons upgrade cannot be done just yet) - source and destination are of the same version
OS: Windows Server 2008 R2 - source and destination are of the same version
We are attempting to move all of our proxy service and mediation development to Developer Studio, which is the approved and supported method. We have installed Developer’s Studio as per the instructions in the installation guide on several workstations. We have succeeded in deploying some simply proxy services to our shared ESB in our integration environment. As long we stick to simple mediators which do not use Xpath things seem to work fine.
Our next step was to attempt to work through the tutorial presented here:
http://wso2.com/library/articles/2014/06/develop-and-deploy-esb-artifacts-using-wso2-developer-studio/
However, when we attempt to use the properties mediator as described in the tutorial, we are unable to save the proxy service. The error message is XPathFactory#newInstance failed to create an XPath for the default object model http://java.sun.com/jaxp/xpath/dom. The end of the error message is "Illegal Configuration-File Syntax".
Version information: WSO2 Dev Studio 3.7.0. JDK 1.7.0_69.
I can't post the stack trace in full because it goes over the 2 link limit, but the first entry is equivalent to the error message.
The expression generating the error is //heal:getHealthCareCenterInfo/heal:longitude/text()
I have a reference to a web service written in java. I need to use it in my BizTalk project. So I add the reference via Add Service Reference - Advanced - Add Web Reference since java web service is not a WCF service. OK, VS generates for me XSDs and ODX for the service. But when I try to compile the project, I get very weird error "Missing partial modifier on declaration of type XXX; another partial declaration of this type exists". The same error is described here.
I thought that I'd missed something so I created a brand new solution, added there a Console Application, added the web reference and that solution builded successfully. Thus I can conclude that I get the error only if I add a web service reference in BizTalk solution.
I tried to fix the error manually, opened the Reference.map.cs file, added ".Biztalk" suffix to the generated namespace and everything compiled successfully. Is it really a bug in code generator for BizTalk project or am I missing something?
Not sure, I have never seen that error...
However, what I would do is create a class library project and add the web reference here. You can then use this in the SOAP send port, as described here (see point #5). You can also reference the class library in your BizTalk project directly. Since you said that the web reference works in a Console application, perhaps this could work...
Also, you could use the XSD schemas directly - but this will require more work. You will have to promote a couple of properties manually in an orchestration or custom pipeline component. You can find more details on this post (website is currently down, but hopefully will be back online eventually).
Finally, you could also try the WCF adapter, using the httpBinding. That's designed for interop and should work as long as you have the schemas to define the messages.
Good luck!
I have an Access 2003 application that communicates with a Webservice to get articles from a central database. It runs fine in a full Access install but when I make runtime install with Package Wizard included in Access 2003 developer extensions, it fails with the error message "429 cannot create an object in the active-x component"
The DLL used for the webservice communication is mssoap30.dll. That dll doesn´t ship with the runtime install and when I try to manually add it to runtime install it is there but when I try to register the DLL it fails with the message:"The register failed reason failed to initiate a DLL" Same result when I put the DLL in the applications folder or in Microsoft shared/Office11. Is there anyone who has made an Access runtime application with web service communication?
If mssoap30.dll is failing to register, that probably means mssoap30.dll itself has dependencies that are missing.
You can download the SOAP Toolkit Installer here:
http://www.microsoft.com/downloads/details.aspx?FamilyID=ba611554-5943-444c-b53c-c0a450b7013c&DisplayLang=en
It's only 1.4 MB, and it should fix the problem. Depending upon what you're using to build your installer, you should be able to embed the SOAP installer and run it during installation (or else just give both files to your users and tell them to install both - that never killed anybody).