访问Windows服务侦听套接字时出现问题 [英] Problem accessing Windows service listening socket

查看:96
本文介绍了访问Windows服务侦听套接字时出现问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我用自定义设置创建了一个Azure SSIS-IR,该自定义设置用于安装我们的产品-该产品作为Windows服务运行,并侦听端口52000上的连接.

I have created an Azure SSIS-IR with a custom setup that installs our product - which runs as a Windows service and listens for connections on port 52000.

安装产品后,我的main.cmd脚本会执行"net start"(网络启动).列出正在运行的Windows服务,并且可以在列表中看到我们产品的服务,因此我知道它已经启动,并且必须已经成功创建了侦听套接字.

After installing the product, my main.cmd script does a "net start" to list the running Windows services, and I can see our product's service in the list, so I know it is start and must have successfully created a listening socket.

然后,我的main.cmd脚本执行"netstat -a"命令.列出所有活动和侦听套接字,但没有提及52000或任何127.0.0.1套接字.

My main.cmd script then does a "netstat -a" to list all the active and listening sockets, but there is no mention of 52000, or any 127.0.0.1 sockets.

果然,当我运行试图连接到该服务的SSIS程序包时,它无法连接.

Sure enough, when I run an SSIS package that attempts to connect to the service, it fails to connect.

我缺少什么?

推荐答案

你好,

您可以手动重新启动产品并查看是否输出任何错误吗?您的产品是否有写入日志? 

Can you manually do a net start of your product and see if it outputs any errors?  Does your product have a log that it writes to?  


这篇关于访问Windows服务侦听套接字时出现问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆