错误信息:No connection could be made because the target machine actively refused it
“错误,连接服务器失败,网络繁忙或者服务器已关闭(状态:正在连接)解决办法
点工具--------账号管理------服务器-------勾选发送服务器需要身份验证
同时要注意自己的端口设置有没有错误,我以前设置端口的时候老是喜欢打错英文字母
1.像这种问题我也出现过,一般多试几次就好了,也有可能对方邮箱已满,提醒对方删除邮箱的邮件,但是记得一定要去网页里删除,在foxmail删除是没有用的,网页里的邮箱还是保存了的
2.程序抛出这个异步目前我已知的有以下几种原因:
1) 操作系统有防火墙,并且阻挡了指定的端口
2)程序被放到宿主程序中,但宿主没有启动
3) Net.Tcp Listener Adapter(NetTcpActivator)服务和Net.Tcp Port Sharing Service(NetTcpPortSharing)没有启动
3.WSAECONNREFUSED (10061) Connection refused . No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host—that is, one with no server application running.An error has occurred while processing the page.Please try to refresh the page, or return to the home page.
4.The following system error occurred : No connection could be made because the target machine actively refused it
以下系统发生的错误:不能做任何连接,因为目标机器积极地拒绝它
error in the OLE DB provider, an error occourred while loading the connection
错误的OLE DB提供者,一个错误occourred而加载连接
以下系统发生的错误:不能做任何连接,因为目标机器积极地拒绝它
error in the OLE DB provider, an error occourred while loading the connection
错误的OLE DB提供者,一个错误occourred而加载连接
5. A running P2V conversion job fails if you create a new conversion job for the same Windows source machine and use a different port to deploy the Converter Standalone agent
If, while running a P2V conversion job, you start creating another conversion job for the sa
If, while running a P2V conversion job, you start creating another conversion job for the sa
me powered on Windows source machine, and specify a port for the connection, Converter Standalone deploys the Converter Standalone agent using the port you specified. If the connection port is different from the one that is being used for the already running conversion job, both jobs fail. The following error message appears in the Job summary tab for the first conversion job: FAILED: A general system error occurred: No connection could be made because the target machine actively refused it. The following error message appears in the Job summary tab for the second conversion job: FAILED: Unable to create a VSS snapshot of the source volume(s). Error code: 2147754774 (0x80042316).
You cannot copy running conversion or configuration jobs
If you open the Copy As New wizard for a running configuration or conversion job when the source is a virtual machine or a backup image and you click Next, the wizard displays the error message Unable to obtain hardware information for the selected machine.
Workaround: Wait for the job to complete before selecting Copy as New in its pop-up menu.
If you open the Copy As New wizard for a running configuration or conversion job when the source is a virtual machine or a backup image and you click Next, the wizard displays the error message Unable to obtain hardware information for the selected machine.
Workaround: Wait for the job to complete before selecting Copy as New in its pop-up menu.
Linked Cloning of source images greater than 2GB to a network share that does not support large files fails
Creating linked clones from source images that are larger than 2GB to a network share that does not support large files (for example, to a Linux SMB share) fails. Converter Standalone does not split the source files into smaller chunks. If the source is larger than the supported file size on the destination, the conversion tasks fails.
Creating linked clones from source images that are larger than 2GB to a network share that does not support large files (for example, to a Linux SMB share) fails. Converter Standalone does not split the source files into smaller chunks. If the source is larger than the supported file size on the destination, the conversion tasks fails.
Conversions of vSphere virtual machine sources with 15 or more disks to any ESX destination managed by VirtualCenter 2.5 fail
If you convert a virtual machine source that resides on an ESX 3.5 host to an ESX 3.5 destination managed by VirtualCenter 2.5, and the source machine has 15 or more VMDK files, the conversion job fails with the following error message in Converter Standalone logs:
FAILED: agent.internal.fault.NfcConnectionFault.summary
Workaround:
If you convert a virtual machine source that resides on an ESX 3.5 host to an ESX 3.5 destination managed by VirtualCenter 2.5, and the source machine has 15 or more VMDK files, the conversion job fails with the following error message in Converter Standalone logs:
FAILED: agent.internal.fault.NfcConnectionFault.summary
Workaround:
Convert the source machine to a hosted virtual machine destination, such as Workstation.
Convert the resulting virtual machine to the ESX managed by VirtualCenter where you want it to reside.
Creating a conversion job to convert a standalone VMware source with a VMDK file greater than 2GB from a network share that does not support large files, fails
If you select a standalone virtual machine source with VMDK file greater than 2GB residing on a remote network location that does not support large files (for example, Linux SMB share), the following error message appears in the Converter wizard on clicking Next orView source details:
Unable to obtain hardware information for the selected machine.
Workaround: Map the network shared folder to the machine where Converter Standalone runs, and select the source from there.
If you select a standalone virtual machine source with VMDK file greater than 2GB residing on a remote network location that does not support large files (for example, Linux SMB share), the following error message appears in the Converter wizard on clicking Next orView source details:
Unable to obtain hardware information for the selected machine.
Workaround: Map the network shared folder to the machine where Converter Standalone runs, and select the source from there.
Converter Standalone cannot detect the power state of VMware Workstation or other VMware hosted source virtual machines if they are located on a read-only network share
If the source machine is a Workstation or another VMware hosted source and is located on
If the source machine is a Workstation or another VMware hosted source and is located on
a network share with read-only permissions, Converter Standalone cannot detect if the source is powered on or suspended. This might lead to data inconsistency on the destination machine if changes are made to the powered on source virtual machine during conversion.
Workarounds:
Workarounds:
Verify that the source virtual machine is powered off prior to conversion.
Provide write privileges to the network share where the source virtual machine resides.
Task progress is not shown when converting a virtual machine that is larger than 1TB dnf接收频道信息失败怎么解决
Converter Standalone does not display the progress of conversion tasks if the source virtual machine is larger than 1TB. Conversion tasks are completed successfully, but the user cannot monitor their progress.
Workaround: You can monitor the disk performance of the destination ESX host to check if tasks are running properly.
Converter Standalone does not display the progress of conversion tasks if the source virtual machine is larger than 1TB. Conversion tasks are completed successfully, but the user cannot monitor their progress.
Workaround: You can monitor the disk performance of the destination ESX host to check if tasks are running properly.
版权声明:本站内容均来自互联网,仅供演示用,请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系QQ:729038198,我们将在24小时内删除。
发表评论