I have created VB.NET application using OPC Labs QuickOPC Classic 5.12 to get the data form the PLC server(SoftwareToolBox's Top server in remote machine). I have configured the DCOM setup in the client machine and server machine. The application is working without any errors, but for past 10 days the applications throws the following error frequently.
A Security Package Specific Error Occurred.
The error is raised by the COM/DCOM infrastructure.
What are the possible reasons/ situations to get this error?
Refer the below link for the answer.
http://www.opclabs.com/forum/connections-reconnections-com-dcom/1778-a-security-package-specific-error-occurred-from-dcom
We are trying to configure continuous integration with TFS 2012. While queuing a new build, the publish fails with the error:
Build FAILED.
"C:\src\ProjectName.sln" (default target) (1) ->
"C:\src\Website\ProjectName.csproj" (default target) (2) ->
(MSDeployPublish target) ->
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Web\Microsoft.Web.Publishing.targets(4377,5): msdeploy error ERROR_COULD_NOT_CONNECT_TO_REMOTESVC: Web deployment task failed. (Could not connect to the remote computer ("ServerName") using the specified process ("Web Management Service") because the server did not respond. Make sure that the process ("Web Management Service") is started on the remote computer. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_COULD_NOT_CONNECT_TO_REMOTESVC)**
I checked all the points mentioned in the IIS.NET documentation for this error. Both services mentioned, Web Management Service and Web Deployment Agent Service, are running fine. A restart of those services has no change in behavior.
Windows Server 2008 R2 with IIS 7.
Web Deployment Agent Service is running on port 8172.
Web Deploy 3.0
Windows Firewall is not blocking any port on the server.
How can this be fixed?
If you install Web Deploy 3.x BEFORE Web Management Tools are installed, you'll have to re-install Web Deploy. I beat my head against the wall for hours on this.
Install the Web Management Services ("Turn Windows Features On/Off"/Roles -> Web Server -> Management Tools -> Management Service)
Then uninstall Web Deploy (repair didn't work) via the usual Add/Remove Programs control panel
Install Web Deploy 3.x again using Web Platform Installer.
Fixed. /Sigh
Double check in your Web Deploy settings that the name of the website is exactly that of what's in IIS.
Ben Day blogged more about it.
Fix that i saw on another website:
Fix it by adding “http://” to server.
In other words, when server is www.xxxx.com would get the 403 error, but when server is http://www.xxxx.com, then it works.
You need also to indicate the app name e.g 'Default Web Site/MyApp'
That was my error. Once I added /MyApp, it worked.
I got this error when using msdeploy, not TFS. In my case I needed to make sure the user msdeploy is using had permission to deploy to the website.
Find the website in IIS manager, right click and go to Deploy, then Configure Web Deploy Publishing. Find the user used by Web Deploy and setup for this website.
In my case the Internet proxy was enabled on source - which made msdeploy to reach out to internet instead of local ICN.
You should check the logs on your IIS first - see that you actually get to the server, and then you can locate the exact error here - https://support.microsoft.com/en-us/help/943891/the-http-status-code-in-iis-7-0-iis-7-5-and-iis-8-0
Uninstalling and re-installing (not repairing!) after setting up IIS did most of the magic for me.
There is another possible cause of the error. IIS Managemente Service have its own configuration for IP Address Restrictions, which default value is Deny Access for unspecified clients (Windows Server 2012 R2 with IIS 8.5).
You must set this value to Allow or add access to your specific IP address/IP address range using the Allow... button.
Remember, you must Stop the Management Service previously to change this configuration.
We're having two systems that are in LAN. Database is in one system
and published files are in another system. Through code the connection is opening
and getting the results, but at publishing time getting "400 Bad Request Error".
If the system having Database, iis in one system at published time also running the
services successfully. But if database is in one system and iis is in another system
then at published time the services are not running.
Please tell me what is the reason and how to resolve that?
I have a .net 2.0 app on a win2003 VM that calls a WCF service hosted in IIS7 on a win 2008 VM. After developing the client and service and testing (all was good) I took the opportunity to take a snapshot of both VMs.
I come back to the VMs two weeks later and when I make the WCF call from the client I get a message dialog on the win 2008 server with the caption "Visual Studio Just-In-Time Debugger". The dialog then reads "An unhandled Microsoft .Net Framework exception occurred in w3wp.exe etc.
I take a look at the WCF service log an now see the following in the "WebHeaders" element:
"VsDebuggerCausalityData" AwAAAOEhpa2...lots of AAA
I've tried reverting both VMs to the previous snapshot but get the same problem.
In the WCF service trace file, I can see the logs entries from just before I took the snapshot and the request / response messages look perfect.
Could anyone please advise next step for diag and fix?
Many thanks
Rob.
Try to invoke WCF from wevservice studio. If you can do it , the problem
is in server.
If problem is in server , you can trace where exactly do you fail
Trace can be done using
http://msdn.microsoft.com/en-us/library/ms732023.aspx
Unfortunately I don't have a lot of technical information to give you but I will give as thorough a description as I can.
I have done a fresh install of Windows Server 2003 Enterprise (SP1). Performed all the updates including SP2 and installed McAfee Enterprise 8.7. Once I've completed doing this I open up the Windows Components installation and check "Application Server" which should install the base IIS installation.
The install runs fine and I reboot just for good measure. When I go into services I see IIS Admin started. Pulling up the IIS Manager reveals that the DefaultAppPool and the Default Web Site are both stopped. Attempting to start the Default Web Site results in no failure message and no entries in the Event Log. This doesn't surprise me terribly as it depends on the DefaultAppPool. When I try to start the DefaultAppPool after a few seconds I get an error "The service did not respond to the start or control request in a timely fashion." and there is still no messages written to the event log.
I've tried this exact installation procedure twice now with identical results. Any suggestions would be greatly appreciated.
I found a work around if not a complete solution. I installed and configured IIS before updating or installing McAfee. IIS worked fine. Since I got it working I didn't want to go back and do a fresh installation but now that I think about it I might have just needed to run updates one more time after installing IIS. The order I installed it did allow me to get it to working so good luck to anyone else that has this issue. I hope this helps.