-
logos
- Influencer
- Posts: 16
- Liked: never
- Joined: May 09, 2013 7:40 am
- Full Name: Logos Technologies
- Contact:
[ERRORS] Cannot use CBT: Soap fault.
hello all,
I open this topic for ask you a question about this error:
We have a PDC with Exchange on board that has had this error in the previous backup schedules:
Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/4fe89ee8-7266c5c6-f20c-5cf3fcb8dd0a/MORO PDC/MORO PDC.vmdkDetail: », endpoint: »
I saw in some other posts 2 solutions:
— Remove all the machine’s shapshots
— Try to reboot the machine.
We tryed to do these 2 tips but has worked nothing.
Some other machine details:
— This machine has the Fileserver Role and it has a disk of 1.5TB for Data
— In this machine there is installed Exchange server 2010.
does anyone know about this error?
Thanks in Advance
-
veremin
- Product Manager
- Posts: 19894
- Liked: 2153 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
-
Contact:
Re: [ERRORS] Cannot use CBT: Soap fault.
Post
by veremin » Sep 09, 2013 1:55 pm
Hi, Logos . Have you also tried to create a new VM snapshot and, then, delete it? According to this user’s experience, it might do the trick. Thanks.
-
foggy
- Veeam Software
- Posts: 20911
- Liked: 2063 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: [ERRORS] Cannot use CBT: Soap fault.
Post
by foggy » Sep 09, 2013 2:01 pm
Also please provide the support case ID for this issue, as requested when you click New Topic, so that we can facilitate and track resolution. Thanks.
-
logos
- Influencer
- Posts: 16
- Liked: never
- Joined: May 09, 2013 7:40 am
- Full Name: Logos Technologies
-
Contact:
Re: [ERRORS] Cannot use CBT: Soap fault.
Post
by logos » Sep 10, 2013 6:44 am
foggy wrote:Also please provide the support case ID for this issue, as requested when you click New Topic, so that we can facilitate and track resolution. Thanks.
i’m sorry i’ll do it. Could you tell me how can i open a support case?
-
logos
- Influencer
- Posts: 16
- Liked: never
- Joined: May 09, 2013 7:40 am
- Full Name: Logos Technologies
- Contact:
Re: [ERRORS] Cannot use CBT: Soap fault.
Post
by logos » Sep 10, 2013 6:46 am
v.Eremin wrote:Hi, Logos . Have you also tried to create a new VM snapshot and, then, delete it? According to this user’s experience, it might do the trick. Thanks.
Hi Eremin,
I did it but nothing has worked.
-
CaptainFred
- Enthusiast
- Posts: 88
- Liked: 2 times
- Joined: Jul 31, 2013 12:05 pm
- Full Name: Si
- Contact:
Re: [ERRORS] Cannot use CBT: Soap fault.
Post
by CaptainFred » Sep 20, 2013 3:46 pm
2 people like this post
I’ve just had this problem on lots of VMs that I can’t have an outage with easily. So we have put together the following script which *seems* to fix it without all the power off/power on/power off steps 
NOTE: Test it on a VM/datastore that you don’t care about just in case! The delete ctk files part is rem’ed out because this wasn’t always necessary. Also change DATACENTER to your datacenter name. 
It does the following:
1. Disables CBT
2. Deletes the *-ctk.vmdk files IF UN-REM’ED
3. Creates a snapshot called CBTFIX
4. Waits
5. Removes the snapshot called CBTFIX
6. Waits
7. Consolidates the disks
8. Waits
9. Enables CBT
Save as CBTFIX.ps1 file and run it:- .CBTFIX.ps1 VMNAME
Code: Select all
$VM = $args[0]
$VMView = Get-VM $VM | Get-VIew
$VMConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec
$vmConfigSpec.changeTrackingEnabled = $false
$vmView.ReconfigVM($vmConfigSpec)
#$Datastore = get-datastore -vm ($VM)
#Rm "vmstore:DATACENTER$Datastore.name$VM*-ctk.vmdk"
New-Snapshot -VM $VM -name CBTFIX
Start-Sleep -S 2
Remove-Snapshot -snapshot (get-snapshot -VM $VM -name CBTFIX) -confirm:$false
Start-Sleep -S 2
$VMCon = Get-VM $VM
$VMCon.ExtensionData.ConsolidateVMDisks()
Start-Sleep -S 1
$vmConfigSpec.changeTrackingEnabled = $true
$vmView.ReconfigVM($vmConfigSpec)
Let me know if it works for you! 
-
eric
- Enthusiast
- Posts: 39
- Liked: never
- Joined: Jan 01, 2006 1:01 am
- Contact:
[MERGED] : Cannot use CBT
Post
by eric » Apr 18, 2014 1:45 pm
Hello All,
Running VBR 7.0.0.839, VMware 5.5 with vCenter
Two configured backup and replication jobs were running fine, now I am seeing this error for a few machines:
4/18/2014 9:09:28 AM :: Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/51350900-33885551-58ed-6cae8b63b452/blahlblah.vmdkDetail: », endpoint: »
This particular replication job is running but will take forever without CBT.
What can I look for?
~eric
-
eric
- Enthusiast
- Posts: 39
- Liked: never
- Joined: Jan 01, 2006 1:01 am
- Contact:
Re: Cannot use CBT
Post
by eric » Apr 18, 2014 2:05 pm
Update: I stopped a replication job that was running, disabled the job, rebooted server, restarted VBR and ran the job again.
The replication job has two virtual machines in it, one completed successfully using CBT and the other one is still failing with the Soap fault error…
~eric
-
veremin
- Product Manager
- Posts: 19894
- Liked: 2153 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
-
Contact:
Re: [ERRORS] Cannot use CBT: Soap fault.
Post
by veremin » Apr 18, 2014 2:30 pm
You can try to reset CBT using procedure described above. If the issue persists, feel free to open a ticket with the support team. Thanks.
-
eric
- Enthusiast
- Posts: 39
- Liked: never
- Joined: Jan 01, 2006 1:01 am
- Contact:
Re: [ERRORS] Cannot use CBT: Soap fault.
Post
by eric » Apr 19, 2014 2:56 pm
v.Eremin wrote:You can try to reset CBT using procedure described above. If the issue persists, feel free to open a ticket with the support team. Thanks.
Okay, I was able to resolve the issue with the KB Article noted above.
The root cause of the problem is that the VMware host had a PSOD.
~eric
Исправления ошибки «Cannot use CBT: Soap Fault. Error caused by file» в программе резирвного копирования Veeam
Veeam – Cannot use CBT: Soap Fault. Error caused by file…
This error happened after a power failure, where my hosts powered down without the guests being powered down first.
Veeam was basically unable to freeze the VM’s to take a hot backup. The backup would complete however, but be extremely slow in the process. This is a result of Changed Block Tracking not telling Veeam what blocks have changed in an incremental (or full) backup.
A lot of sites, including Veeam’s KB page, have suggested changing the CBT parameters in the offending VM’s, but this involves shutting down the guests.
What worked for me was much less invasive.
Edit the existing Veeam job, and click on Virtual Machines
Click the Recalculate button to the right. I initially saw the calculated size was indeed zero, so it had no idea of the machine sizes it was backing up
Once the machines/folders have recalculated and you have sizes populated, click Finish. This should then re-populate the Veeam database.
Hopefully you’ll have no more warnings, and also have a much faster backup timeframe.
А теперь все просто и по русски …..
Jobs — Backup выбираем наше задания — Edit — Virtual Mashines — и справа в низу кнопка Recalculate. После пересчета все сохраняем и запускаем заново наше задания.
We frequently see errors like this in our backup jobs:
10/05/2013 12:21:18 :: Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/781f6afc-ea228458/VDED-CIT-010(Exchange EX01)/VDED-CIT-010(Exchange EX01).vmdkDetail: '', endpoint: ''
In the last job that ran 11 out of 235 VMs backed up had this as a warning.
As a full example here’s the output from statistics for one VM:
09/05/2013 22:02:14 :: Queued for processing at 09/05/2013 22:02:14
12/05/2013 02:30:00 :: Required backup infrastructure resources have been assigned
12/05/2013 02:30:02 :: VM processing started at 12/05/2013 02:30:02
12/05/2013 02:30:02 :: VM size: 20.0 GB (3.9 GB used)
12/05/2013 02:30:02 :: Using source proxy 10.24.0.11 [nbd]
12/05/2013 02:30:36 :: Creating VM snapshot
12/05/2013 02:30:46 :: Saving '[SAN3-NFS2] VDED-IL-001(LB)/VDED-IL-001(LB).vmx'
12/05/2013 02:30:51 :: Saving '[SAN3-NFS2] VDED-IL-001(LB)/VDED-IL-001(LB).vmxf'
12/05/2013 02:30:56 :: Saving '[SAN3-NFS2] VDED-IL-001(LB)/VDED-IL-001(LB).nvram'
12/05/2013 02:31:01 :: Hard Disk 1 (20.0 GB)
12/05/2013 02:31:14 :: Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/ca67d9a6-d95e1a1f/VDED-IL-001(LB)/VDED-IL-001(LB)-000001.vmdkDetail: '', endpoint: ''
12/05/2013 02:42:17 :: Removing VM snapshot
12/05/2013 02:42:21 :: Finalizing
12/05/2013 02:42:30 :: Network traffic verification detected no corrupted blocks
12/05/2013 02:42:30 :: Busy: Source 99% > Proxy 4% > Network 0% > Target 0%
12/05/2013 02:42:30 :: Primary bottleneck: Source
12/05/2013 02:42:30 :: Processing finished with warnings at 12/05/2013 02:42:30
My question is:
- What does this error mean exactly?
- If it’s a problem (I think it makes VMs transfer the whole disk rather than changes, so it’s not ideal) how can I fix it?
asked May 12, 2013 at 21:23
1
The error means that Veeam cannot identify what blocks have changed. This could have numerous causes, for example, your storage was powered down without to shut down the VMs via guest OS first.
The fix is fairly simple but it does require powercycling the VM, see KB:1113 — How to reset CBT. From the KB article:
- Power off the VM
- Right click the VM, click «Edit settings», find the «Options» tab and click «Configuration Parameters»
- Set the «ctkEnabled» value to false
- Set the «scsi0:x.ctkEnabled» value to false for each disk of the VM in question5. Open the source folder and remove any -CTK.VMDK files.
- Power on the VM
- Power off the VM again. This step is needed to update the CTK table.
- Power on the VM
- Rerun Backup or Replication job to re-enable CBT
answered May 12, 2013 at 22:00
I have the same issue after an unexpected power failure. I got the issue resolved by creating a snapshot of each vms and deleted. then run the Backup and worked
answered May 3, 2017 at 11:21
Содержание
- Veeam R&D Forums
- Error: Cannot get service content
- Error: Cannot get service content
- Re: Error: Cannot get service content
- [MERGED] cannot get service content soap found. host not fo
- [MERGED] cannot get service content soap found. host not fo
- Re: cannot get service content soap found. host not found
- [MERGED] ProcessingMyVM Error: Cannot get service content.
- Re: Error: Cannot get service content
- Who is online
- Veeam R&D Forums
- [ERRORS] Cannot use CBT: Soap fault.
- [ERRORS] Cannot use CBT: Soap fault.
- Re: [ERRORS] Cannot use CBT: Soap fault.
- Re: [ERRORS] Cannot use CBT: Soap fault.
- Re: [ERRORS] Cannot use CBT: Soap fault.
- Re: [ERRORS] Cannot use CBT: Soap fault.
- Re: [ERRORS] Cannot use CBT: Soap fault.
- Re: [ERRORS] Cannot use CBT: Soap fault.
- Re: [ERRORS] Cannot use CBT: Soap fault.
- Re: [ERRORS] Cannot use CBT: Soap fault.
- Veeam R&D Forums
- [Resolved] Soap faul & Failed to upload disk. Agent failed to process method
- [Resolved] Soap faul & Failed to upload disk. Agent failed to process method
- Re: Soap faul & Failed to upload disk. Agent failed to process method
- Re: Soap faul & Failed to upload disk. Agent failed to process method
- Re: Soap faul & Failed to upload disk. Agent failed to process method
- Re: Soap faul & Failed to upload disk. Agent failed to process method
- Re: Soap faul & Failed to upload disk. Agent failed to process method
- Re: Soap faul & Failed to upload disk. Agent failed to process method
- Who is online
- Veeam R&D Forums
- SOAP connection is not available
- SOAP connection is not available
- Re: SOAP connection is not available
- Re: SOAP connection is not available
- Re: SOAP connection is not available
- Re: SOAP connection is not available
- Re: SOAP connection is not available
- Re: SOAP connection is not available
- Veeam R&D Forums
- Failed to login to vCenter Server by SOAP, port 443
- Failed to login to vCenter Server by SOAP, port 443
- Re: Failed to login to vCenter Server by SOAP, port 443
- Re: Failed to login to vCenter Server by SOAP, port 443
- Re: Failed to login to vCenter Server by SOAP, port 443
- Re: Failed to login to vCenter Server by SOAP, port 443
- Re: Failed to login to vCenter Server by SOAP, port 443
- Re: Failed to login to vCenter Server by SOAP, port 443
Veeam R&D Forums
Technical discussions about Veeam products and related data center technologies
Error: Cannot get service content
Error: Cannot get service content
Post by eitand84 » May 01, 2016 1:31 pm this post
Re: Error: Cannot get service content
Post by Shestakov » May 01, 2016 2:41 pm this post
[MERGED] cannot get service content soap found. host not fo
Post by dmb2002man » Jul 12, 2016 1:17 pm this post
I am running version 8.0. I had to restore a valid server from veeam when it wouldn’t boot up and now having issues with it not backing up. cannot get service content soap fault. host not found. I can ping the host from the veam that this server is on and ping vcenter. Also can pull up vcenter browser from the veeam server. Soap connection is not available. I tried to remove the server from backup and re-add it. All the other servers on that host are backing up fine. This is the only one having issues.
[MERGED] cannot get service content soap found. host not fo
Post by foggy » Jul 12, 2016 1:30 pm this post
Re: cannot get service content soap found. host not found
Post by dmb2002man » Jul 12, 2016 2:13 pm 1 person likes this post
[MERGED] ProcessingMyVM Error: Cannot get service content.
Post by emmoon1981 » Oct 24, 2016 2:04 pm this post
Hi All
I have a problem during backing up from a virtual machin and face whit this error :
» ProcessingMyVM Error: Cannot get service content.
Soap fault. TimeoutDetail: ‘connect failed in tcp_connect()’, endpoint: ‘https://myhost:443/sdk’
SOAP connection is not available. Connection ID: [«myhostIP»].
Failed to create NFC download stream. NFC path: [nfc://conn:myHost,nfchost:ha-host,stg:54a69d54-13ddb6c0-dc50-40a8f027fdac@MyVM/MyVM.vmx].»
In addition My Host running VMWare esxi6u2 in another site and every thing about my connection is OK and open and I Installed VBR9U1 in standalone system and make a backup job that set repository and Proxy server Both in remote Host and I tested the job for any Vm on that remote Host
Appreciate any insights.
Re: Error: Cannot get service content
Post by PTide » Oct 24, 2016 2:35 pm this post
Please contact the support team and post your case ID here.
Who is online
Users browsing this forum: No registered users and 11 guests
- Main
- All times are UTC
- Delete cookies
- Members
- The team
- Contact us
DISCLAIMER: All feature and release plans are subject to change without notice.
Powered by phpBB® Forum Software © phpBB Limited
Источник
Veeam R&D Forums
Technical discussions about Veeam products and related data center technologies
[ERRORS] Cannot use CBT: Soap fault.
[ERRORS] Cannot use CBT: Soap fault.
Post by logos » Sep 09, 2013 1:37 pm this post
hello all,
I open this topic for ask you a question about this error:
We have a PDC with Exchange on board that has had this error in the previous backup schedules:
Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/4fe89ee8-7266c5c6-f20c-5cf3fcb8dd0a/MORO PDC/MORO PDC.vmdkDetail: », endpoint: »
I saw in some other posts 2 solutions:
— Remove all the machine’s shapshots
— Try to reboot the machine.
We tryed to do these 2 tips but has worked nothing.
Some other machine details:
— This machine has the Fileserver Role and it has a disk of 1.5TB for Data
— In this machine there is installed Exchange server 2010.
does anyone know about this error?
Thanks in Advance
Re: [ERRORS] Cannot use CBT: Soap fault.
Post by veremin » Sep 09, 2013 1:55 pm this post
Re: [ERRORS] Cannot use CBT: Soap fault.
Post by foggy » Sep 09, 2013 2:01 pm this post
Re: [ERRORS] Cannot use CBT: Soap fault.
Post by logos » Sep 10, 2013 6:44 am this post
Re: [ERRORS] Cannot use CBT: Soap fault.
Post by logos » Sep 10, 2013 6:46 am this post
Re: [ERRORS] Cannot use CBT: Soap fault.
Post by logos » Sep 10, 2013 6:51 am this post
Re: [ERRORS] Cannot use CBT: Soap fault.
Post by foggy » Sep 10, 2013 7:10 am this post
Re: [ERRORS] Cannot use CBT: Soap fault.
Post by logos » Sep 16, 2013 8:41 am this post
On Wednesday I’m going to modify this parameter.
I’ll keep you updated.
have a nice day
Re: [ERRORS] Cannot use CBT: Soap fault.
Post by CaptainFred » Sep 20, 2013 3:46 pm 2 people like this post
I’ve just had this problem on lots of VMs that I can’t have an outage with easily. So we have put together the following script which *seems* to fix it without all the power off/power on/power off steps
NOTE: Test it on a VM/datastore that you don’t care about just in case! The delete ctk files part is rem’ed out because this wasn’t always necessary. Also change DATACENTER to your datacenter name.
Источник
Veeam R&D Forums
Technical discussions about Veeam products and related data center technologies
[Resolved] Soap faul & Failed to upload disk. Agent failed to process method
[Resolved] Soap faul & Failed to upload disk. Agent failed to process method
Post by y0da » Oct 31, 2018 2:13 pm this post
The server has 5 hard drives and backups up 3 out of 4 with no issue. It is failing on 2 hard drives every time.
I am in the processing of vmotion’ing those 2 drives to another datastore then back to see if that helps. I have also rebooted the veeam backup server and associated proxies to see as well.
Re: Soap faul & Failed to upload disk. Agent failed to process method
Post by wishr » Oct 31, 2018 2:23 pm this post
Could you please take a look at that thread while continue working with our support team? I believe your cases are similar.
Re: Soap faul & Failed to upload disk. Agent failed to process method
Post by y0da » Oct 31, 2018 2:27 pm this post
Could be — hard to say. The DataTranfer.Sync disk elludes to many different things. After the vmotion though I will attempt a chkdsk on both disks. Granted they are literally 1 or 2 weeks old (not that that means anything).
Re: Soap faul & Failed to upload disk. Agent failed to process method
Post by y0da » Oct 31, 2018 3:08 pm 1 person likes this post
Re: Soap faul & Failed to upload disk. Agent failed to process method
Post by y0da » Nov 01, 2018 12:52 pm this post
vMotioning the drive to another datastore allowed the backup to complete. I am currently moving it back to its original store and will report back to see if they are still successful.
One thing I noticed but it may have been my eyes playing tricks on me. I believe this drive i moved had the same name xxxxx.vmdk as another hard drive on this server but they were in two different datastores — but after the migration it appears to be named properly. not sure if this makes sense but I wanted to add that.
Re: Soap faul & Failed to upload disk. Agent failed to process method
Post by y0da » Nov 02, 2018 1:01 pm this post
This worked. Now that it is back in the original datastore the job ran fine.
Again I only moved one problematic vmdk and moved it back and that solved the issue.
Not sure if it was bit rot cause the other drive was failed also, but all is well in the world again.
Re: Soap faul & Failed to upload disk. Agent failed to process method
Post by wishr » Nov 02, 2018 2:45 pm this post
Glad to see it works now and thank you for sharing your feedback — it’s highly appreciated!
Who is online
Users browsing this forum: No registered users and 11 guests
- Main
- All times are UTC
- Delete cookies
- Members
- The team
- Contact us
DISCLAIMER: All feature and release plans are subject to change without notice.
Powered by phpBB® Forum Software © phpBB Limited
Источник
Veeam R&D Forums
Technical discussions about Veeam products and related data center technologies
SOAP connection is not available
SOAP connection is not available
Post by TMassa » Mar 16, 2010 8:22 pm this post
My environment:
EVALUATING Veeam
8 ESX hosts in a single cluster. ESX 4 u1 (vSphere). All new and installed in the last 3 weeks.
Veeam B&R installed on physical host with an iSCSI connection to the same SAN as the ESX cluster. 1.5 TB for testing.
I have just installed Veeam B&R and I am attempting to backup my first VM. I can successfully connect to the VC and ESX server to see all of the data, but when I try to backup any VMware clients, the initial VBK file gets created on the iSCSI storage drive(V:), then the job fails with the following error:
I can’t figure out why I can browse all of the datastores, but can’t login over SOAP. Is this a problem with a VMware config and not your product?
-Thanks in advance
Re: SOAP connection is not available
Post by Gostev » Mar 16, 2010 8:56 pm this post
Re: SOAP connection is not available
Post by TMassa » Mar 16, 2010 9:15 pm this post
I have changed the account to use my VC login account with the same result. The web services was not enabled on the ESX host, and has been enabled, but I’m not sure if that alone would work since the Veeam app is trying to connect to https://my-vc-server:443/sdk, and not the ESX host. When I look at the VC Server settings, Advanced Settings:
VirtualCenter.VimApiUrl is currently set to https://my-vc-server:443/sdk
Would the vSphere Web Services API be enabled by default? It really appears to be just down.
Re: SOAP connection is not available
Post by Gostev » Mar 16, 2010 10:13 pm this post
Re: SOAP connection is not available
Post by TMassa » Mar 17, 2010 1:05 pm this post
Re: SOAP connection is not available
Post by Gostev » Mar 17, 2010 1:45 pm this post
Re: SOAP connection is not available
Post by TMassa » Mar 17, 2010 1:54 pm this post
I’ll do that after I rebuild my test machine with 2008 R2. It’s currently on 2003 R2, which was used to test another app.
I did notice that I also got the following event in the Application event log; however, the errors do not correspond to the same time as the failed backups:
Event Type: Error
Event Source: VeeamLog
Event Category: None
Event ID: 1
Date: 3/17/2010
Time: 3:19:34 AM
User: N/A
Computer: MY-BACKUP-SERVER
Description:
Failed to add declaration
System.Runtime.InteropServices.COMException (0x80010002): Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at System.Management.ManagementObject.Initialize(Boolean getObject)
at System.Management.ManagementClass.GetInstances(EnumerationOptions options)
at Veeam.Backup.Common.EnvironmentEx.GetCpuInfo()
at Veeam.Backup.Common.VLog.BuildDeclaration(StringBuilder sb)
at Veeam.Backup.Common.VLog.AddDeclaration()
I’ll post the results using 2008 R2 on a clean install. Thanks for your help.
Источник
Veeam R&D Forums
Technical discussions about Veeam products and related data center technologies
Failed to login to vCenter Server by SOAP, port 443
Failed to login to vCenter Server by SOAP, port 443
Post by roberi » Aug 29, 2013 8:48 am this post
I have a Veeam 6.5 that’s been working very good for a few weeks since I upgraded to VMware 5.1.
But this night I have an error.
«Failed to login to vCenter Server by SOAP, port 443, user » Domainadministrator», proxy srv; port 0. Cannot complete login due to an incorrect user name or password»
Half of the jobs ran OK but the other half failed. I cannot edit the jobs. same error. I cannot edit the server. same error.
I tried to add the server with DNS-name this time but I get the same error.
Patch 3 is installed.
I can login with the same user on the vCenter and the Veeam server so account is OK.
Anyone have any idea??
Re: Failed to login to vCenter Server by SOAP, port 443
Post by Dima P. » Aug 29, 2013 9:50 am this post
Possibly, your vCenter database is on the SQL Server Express Edition, which has a 4 GB of data limitation. If the vCenter database is full, every new transaction is written to cache, as a result when the cache is full, the database service will just stop. The cache gets cleared after a reboot of the vCenter Server, so vCenter starts to work until the cache is exhausted again.
Could you please double check that your vCenter database is not over 4 Gigs?
Thank you.
Re: Failed to login to vCenter Server by SOAP, port 443
Post by roberi » Aug 29, 2013 12:04 pm this post
Its only on 1.8GB, and its a Express 2008R2 so the limit is 10GB I think?!
Thank you.
br
Robban
Re: Failed to login to vCenter Server by SOAP, port 443
Post by Dima P. » Aug 29, 2013 3:17 pm this post
Robban, thank you for clarifying!
Any chance you changed account permissions/or user account group? Any changes with SSO server itself?
Also please double check this solution:
Re: Failed to login to vCenter Server by SOAP, port 443
Post by roberi » Aug 30, 2013 6:30 am this post
Well. last night replication was OK.
hmmm I don’t know why.. but it seems to be okey now. I will see if it happens again tonight.
Re: Failed to login to vCenter Server by SOAP, port 443
Post by veremin » Aug 30, 2013 7:49 am this post
Yep, as far as I know, the database size limit has been increased for SQL Server 2008 R2 Express. So, the Maximum database size in SQL Server 2008 R2 is 10 GB.
As to the issue itself, I glad to hear that it went away. Though, keep us updated how things will be going in your environment. Thanks.
Re: Failed to login to vCenter Server by SOAP, port 443
Post by roberi » Sep 03, 2013 7:15 am this post
Now my second Cluster starts acting almost the same. Also a 5.1.
Veeam reports bad user or password. I can only login localy to vCenter on the vCenter server. with remote vCenter clients I get the same error. Its been working OK for a few weeks also.
It seems to be vCenter related then.
I will investigate further.
Источник
Hello,
I have encountered this warning on Veeam Backup & Replication version 6.1.0.205 on one Exchange Server 2007 VM.
The issue started the backup wants to run, but Veeam was unable to freeze the guest machine to take hot backup, and the snapshot left inside the datastore of the VM and Veeam didn’t remove it. Veeam job was configured to re-try the failed job after 15 minuets. Again, when it’s started, the Veeam created a snapshot and when it failed, Veeam didn’t remove the snapshot. This issue has caused the datastore to be filled up and left without space 
Manually, I consolidated all the snapshots and deleted all of them. Then when I started the VM, luckily started fine.
But, when I re-run the Veeam Job, it started but very slow and gives the following warning. Cannot use CBT: Soap fault. Error caused by file.
Solution:
Edit the Veeam Backup Job, and in the Virtual Machines section, hit the button Recalculate. This will recalculate the exchange disks and will be re-added veeam/vCenter database. After that, the job started as incremental without warning and full backup without warning and faster
Thanks,
by, Cannot, Caused, CTP, Error, Fault, file, Soap, use
This entry was posted on October 7, 2012, 10:33 am and is filed under Veeam Backup & Replication. You can follow any responses to this entry through RSS 2.0.
You can leave a response, or trackback from your own site.