2023年12月7日发(作者：)
错误信息：No connection could be made because the target machine actively refused it
“错误,连接服务器失败,网络繁忙或者服务器已关闭(状态:正在连接)解决办法
点工具--------账号管理------服务器-------勾选发送服务器需要身份验证
同时要注意自己的端口设置有没有错误，我以前设置端口的时候老是喜欢打错英文字母
1.像这种问题我也出现过，一般多试几次就好了，也有可能对方邮箱已满，提醒对方删除邮箱的邮件，但是记得一定要去网页里删除，在foxmail删除是没有用的，网页里的邮箱还是保存了的
2.程序抛出这个异步目前我已知的有以下几种原因:
1) 操作系统有防火墙，并且阻挡了指定的端口
2)程序被放到宿主程序中,但宿主没有启动
3) Listener Adapter(NetTcpActivator)服务和 Port Sharing
Service(NetTcpPortSharing)没有启动
NNREFUSED (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 error has
occurred while processing the try to refresh the page, or return to the home page.
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而加载连接
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 same
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.
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.
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: y
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.
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 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:
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
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.
Conversion jobs from and to ESX hosts that are not connected to vCenter Servers fail if the
number of disks on the source machine is more than nine
When converting a source machine that has more than nine disks, conversion fails with the
following error in the log file:
Error on logout (ignored): Operation timed out
SSLStreamImpl::BIORead (3BBA4E8) timed out.
The error is due to the limited number of NFC connections that can be established to ESX hosts
that are not connected to vCenter Servers.
Workaround: Connect to the destination ESX host through a vCenter Server. In this case, the
number of source disks is limited to 27 for ESX and to 23 for ESXi hosts.
Converting source volumes with unrecognized file systems might prevent the destination
virtual machines from starting While you are setting up a volume-based cloning task in one of the Converter Standalone wizards,
the volume name might be missing in some rows of the Source Volumes tab. This means that
Converter Standalone does not recognize the file system on those volumes. The destination
virtual machine that is created as a result of such a conversion task might fail to start up.
Nevertheless, Converter Standalone copies the source volume data to the destination using
block-level copying.
Workaround: configure the destination virtual machine after the conversion.
Converting standalone VMware sources with a VMDK file greater than 2GB to a hosted
destination that resides on a network share that does not support large files, fails
If you select a standalone virtual machine source with VMDK file greater than 2GB and try to
convert it to hosted destination residing on a remote network location that does not support
large files (for example, Linux SMB or NFS share), the conversion job might fail with one of
following error messages:
Unable to connect to the virtual disk
Remote server closed connection after 0 response bytes read
An error occurred during an operation on a virtual disk
.
If conversion is successful, the following error message related to the VMDK file might
appear when you power on the destination virtual machine:
Internal Inconsistency errors
Workaround:
In the main application window of Converter Standalone, right-click the failed job and
select Copy
Go to the Options page and select Data to Copy.
In the Data to Copy pane, select the volumes to copy and click Advanced.
On the Destination layout tab, select 2GB Split not pre-allocated or 2GB Split
pre-allocated as the destination disk type.
Click Next to view a summary of the conversion job.
On the Ready to Complete page, click Finish to resubmit the job.
Converter Standalone is unable to detect the system volume if it resides on a SCSI disk and
IDE disks are present in the source machine
On source machines with SCSI and IDE disks, Converter is unable to detect the system volume if
the system volume resides on a SCSI disk. Converter only checks the first IDE disk in such
configurations.
If the hardware configuration of the source machine is modified while the Conversion wizard
is open, you need to restart the conversion wizard if you want to view correct source details
Source machine details are retrieved per wizard session, as this is a time-consuming process. If
some changes occur on the source machine (such as adding memory or hard drives) after this
information is retrieved, the Conversion wizard does not show information about the changes.
Workaround: Restart the conversion wizard.
Cloning a source that contains file system errors might result in a damaged virtual machine
See Cloning a source that contains file system errors may result in a damaged copy (KB 1006689).
Timeout on SSL handshake when converting over a WAN link
Converter Standalone does not support conversion over a WAN. When trying to perform a conversion over a WAN link, you might experience an SSL timeout because the timeout for SSL
handshakes is two minutes.
Workaround:
To avoid the two-minute handshake, perform a conversion to a hosted destination machine
(for example, Workstation) in the same LAN.
Copy the temporary virtual machine and send it over the WAN to the remote site.
If the intended destination is a Workstation virtual machine, this completes the process.
If the intended destination is ESX, import the Workstation virtual machine to the ESX server.
User Account Control (UAC) prevents installing Converter Standalone agent if you are not
using the default Administrator account to connect to a powered on source machine
If you are setting up a task to convert a powered on source machine that runs Windows Server
2008, Windows Vista, or Windows 7 and you use a non-default Administrator account to log in to
the source machine, the following error message might appear when you try to install Converter
Standalone agent on the source machine: Insufficient permissions to connect to xxxxxxx.
Here xxxxxxx is the IP address of the source machine. This is because Converter Standalone
server cannot install Converter Standalone agent when UAC is enabled and you are logged in to
the source as non-default Administrator user.
Workaround: Disable the UAC on the source machine before you start the Conversion wizard. You
can search the Microsoft Web site for procedures on disabling the UAC depending on the source
operating system.
The Reconfigure Virtual Machine wizard does not display correctly the vDS port group name
When you reconfigure a virtual machine that uses dvSwitch and you navigate to the Network
interface settings pane, the Network name text box does not display the name of the dvSwitch
after the port group name. Only port group is displayed instead.
The reported network transfer rate might not be correct
The reported network transfer rate might be higher than the actual one because of the inherent
compression used by the network protocol. This does not affect the network throttling.
Adding a virtual machine to a domain might fail if you specify a fully qualified user name
When configuring a virtual machine, you might not be able to add the virtual machine to a
domain if you use a fully qualified user name (DOMAIN_NAME/USER_NAME).
Workaround: Specify the user name without including the domain name.
Conversion of a physical machine running Microsoft Windows XP or Windows Server 2003
with a BCD manager (Boot Manager for Windows Vista) and later might fail
If you try to convert a physical machine with a BCD manager, the P2V conversion might fail in the
following cases:
Microsoft Windows Vista or later is installed on the source physical machine, which is a
dual-boot machine currently running Microsoft Windows XP or Windows Server 2003.
Microsoft Windows Vista or later is installed as a second operating system on the source
physical machine and later is removed, but the BCD manager is left on the source machine.
Workaround 1: In case of a dual-boot machine conversion :
Boot the later version of Windows (Windows Vista, Windows Server 2008, or Windows 7).
Perform a physical source conversion.
On the newly created virtual machine, boot a repair CD for the earlier version of Windows
(Windows XP or Windows Server 2003). Remove the BCD manager and revert the operating system to its compatible boot process.
Shut down the virtual machine and reconfigure it by using the Converter Standalone
configuration wizard. Now you can boot the machine.
Workaround 2: In case of converting a source machine running Windows XP or Windows
Server 2003 with a BCD manager:
On the source machine, boot a repair CD of the corresponding operating system.
Remove the BCD manager and revert the operating system to its compatible boot process.
For more information on how to repair BCD, see the Microsoft knowledge base
article Windows no longer starts after you install an earlier version of the Windows operating
system in a dual-boot configuration.
You cannot perform a P2V conversion without having administrative privileges
If you start the Converter Standalone client under the context of a non-administrative user, you
will not able to perform a remote physical to virtual migration.
Workaround: Start the Converter Standalone client under the context of a user with
administrative privileges.
Conversion fails if the datastore name contains the @ symbol
If the datastore name of the managed source or destination contains "@", the conversion fails.
Workaround: Remove the @ symbol from the datastore name and perform the conversion.
Submitting a job might fail with The specified parameter was not
correct:""message
If Converter Standalone is installed in a client-server mode and you have connected with a
Windows domain username by entering the IP address or the host name of the Converter server,
submitting a job might fail with The specified parameter was not correct:"" message.
Workaround: Connect either to a local server or by using a local username instead of a domain
one.
You might not be able to convert more than nine disks at once
On ESX 3.5 and 4.0, conversion might fail if you try to convert more than nine disks.
Workaround: Perform conversion in multiple steps to convert the disks in portions of up to nine.
Then, attach all the disks to the target machine.
发布评论