Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." Tried suggestions I've seen on the forum.

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." I've tried various suggestions I've seen on the forum but nothing has worked. TIme Machine worked fine for the last two years and just suddenly started having this problem every time. The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned. I have more than enough available backup storage space for it. Before failing, Time Machine has backed up no more than 12GB or so of the backup. It fails during different files each time.
I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem. It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine.
I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
I have system logs that I can share if helpful. The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
I always get this message near the beginning of the backup:
Event store UUIDs don't match for volume: Macintosh HD
I've gotten this messsage a number of times:
Bulk setting Spotlight attributes failed.
One Day
Stopping backupd to allow ejection of backup destination disk!
Another day
1/7/12 10:44:20 AM
mDNSResponder[18]
PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
1/7/12 10:46:37 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
1/7/12 10:46:37 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
Another Day
1/6/12 8:03:22 AM
Google Chrome[164]
Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
1/6/12 8:04:02 AM
com.apple.backupd[193]
Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
1/6/12 8:06:58 AM
/System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
No valid tickets, timing out
1/6/12 8:29:44 AM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
1/6/12 8:59:22 AM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/TimeMachine
1/6/12 8:59:22 AM
kernel
ASP_TCP asp_SetTCPQoS: sock_settclassopt got error 57
Another day
1/5/12 3:48:55 PM
mdworker[2128]
CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
1/5/12 4:24:54 PM
mDNSResponder[19]
PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
1/5/12 4:29:58 PM
com.apple.backupd[2074]
Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
1/5/12 4:39:00 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

bokon0n wrote:
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
1/11/12 8:53:30 AM
com.apple.backupd[1169]
Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
Those indicate that your NAS is not fully compatible with Snow Leopard.
1/11/12 8:53:35 AM
kernel
jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
1/11/12 8:53:39 AM
kernel
jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
1/11/12 8:53:49 AM
kernel
jnl: disk2s2: journal replay done.
1/11/12 8:53:49 AM
fseventsd[41]
event logs in /Volumes/Time Machine/.fseventsd out of sync with volume. destroying old logs. (253512 14 253512)
1/11/12 8:53:50 AM
kernel
hfs: Removed 1 orphaned / unlinked files and 0 directories
That looks like a problem was found with the file system (data) on the TM disk. I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive. Likely a result of the incompatibility mentioned above.
1/11/12 9:47:40 AM
com.apple.backupd[1169]
Bulk setting Spotlight attributes failed.
That's a problem writing to the NAS drive.
But the backup continued after all this.
1/11/12 1:25:07 PM
kernel
ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
Something caused a disconnect. Can't tell from the log what it was.
I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
To be incompatible with Snow Leopard, this NAS must be at least a couple of years old. It may be beginning to fail.
Contact the maker. See if there's an update to make it compatible with Snow Leopard. If so, that might fix it.
If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

Similar Messages

Time Machine couldn't complete the backup due to a network problem

Firstly apologies for the long post, I've been bottling these problems up and could now use some expert advice.
I have a MacPro (10.6.3) with four internal drives (320GB system/apps. + 3x 750GB data, images etc) and a MacBook Pro (10.6.6) with a 320GB internal. With so much accumulated data (Mac user since SE FDHD) I wanted a reliable means to backup all my projects, books, papers, research, images etc. I had several bad experiences using Iomega drives (Ultramax and Storcentre) which were not very Mac compatible and shifted over to a 10TB LaCie 5Big Network 2 which is promoted as Time Machine compatible. Set up Time Machine (with a few hiccups) in Sept 2010 and it ran perfectly, backing up both main computers until March 2011. I have now experienced a string of problems backing up the MacPro, some of which have been resolved speaking to people, some by checking forums and some by using my own noddle to figure it out. The latest error message I am getting is "Time Machine couldn't complete the backup due to a network problem. Make sure your computer and the backup disc are on the same network, and that the backup disc is turned on. Then try again to back up."
The circumstances of this are as follows: TM seems to be trying to completely back up everything already backed up from previous months so I am using the "exclude" option to do this in manageable chunks (5.54TB of 7.99TB is available so there is a lot of stuff on there, hence my reticence to erase and start again). I started a backup last night which said it was 242GB and when I came back hours later (I estimate 30GB and hour or 500MB a minute) it has failed with the error message above. I asked it to back up again and it said it now had 191GB to backup, at the next failure it was 142GB, dropping by approx 50GB a time (if there a maximum it can manage in one go?), the next time it was starting again with 242GB.
I checked the disc it was backing up to, discovered it was now selecting Public-1, re-selected Public which houses the macpro.sparsebundle, dropped the backup size (Options) to 73GB and set it off again and it is backing up as I write. I am hoping it will complete and permit another chunk to be backup but the fact it looses network connection (seemingly) or has a maximum backup in one go, is annoying because it means you cannot leave it overnight and trust it to do the backups.
The other problem seems to be a shut down by LaCie 5Big because several times (and once this morning) I have had this message "The file server "LaCie 5Big" has closed down, followed by a complete Lacie shut down and auto-reboot with all lights and whistles. Lacie think this could be a power supply problem and say they are sending me another power brick. They also say they do not support Time Machine (they should check their own literature) and suggest I use LaCie 5Big for 'drag and drop' backup. If I wanted to do that I could pick up a cheap and nasty HD from PCWorld, not this high end 10TB drive which cost over £1,000 !
For a while y'day I could not even find the Lacie on the network but after changing the ethernet cable from Lacie to router (Linksys) it miraculously re-appeared so that problem may have been the original Lacie blue ethernet cable had developed a fault. Checking cables is an oft-overlooked option.
A catalogue of errors, some solved, others still all pervading, so any words from the wise would be gratefully accepted.

I verified the macpro.sparsebundle and Time Machine backups in Disk Utility and it said both appeared to be Okay in green type. So that did not solve the issue. I did a Disk Utility repair a day or so again (despite Verify saying everything was fine) and said there was nothing to repair. I suspect two problems, the power brick may be faulty producing intermittent power and maybe causing the drive to close down (hopefully Lacie will send me a replacement to try) and second, I am thinking the network connection is getting dropped causing crashed backups without the Lacie shutdown/reboot sequence. The 73GB back up failed, I started it again at 54GB and it failed again, just started it again at 45GB - this is no way to progress!
Perhaps the relatively new (last year) Linksys router is the problem, I find my MBP says AirPort is active but it fails to appear in Go>Server unless I switch it off and on again and perhaps a similar problem drops the connnection to the Lacie.

I loaded in Lion - but my time capsule will not back up. I get an message: couldn't complete backup due to a network prolem. Also it says "make sure your computer and back up disk are on the same network, and that the backup disk is turned on.

I installed Lion on my Mac Pro laptop. Regarding Time Capsul - I get a messaage as follows: couldn't complete backup due to a network problem. Make sure your computer and back up disk are on the same network and that the backup disk is turned on. Then try again to back up. I have time capsul turned on. bill

I have exactly same problem with my MBP and MBA, after upgrading to Lion. I've tried to fix this issue while cheking key chain issues and network setup, even formating hdd and time capsule firmware upgrade (ver. 7.6.1.). Nothing can help. It is very annoying.

Systemd: some services starting too early and then failing

Hello everyone,
I freshly installed Arch on this new laptop (Asus Zenbook Prime UX32VD) and from the start, I wanted to have a pure systemd setup. I'm using services only and I've uninstalled initscripts and so far it's working relatively well.
However, some services seem to start too early by default and the workarounds are unsatisfactory.
Problem 1: asus-screen-brightness and asus-kbd-backlight
On this lap top, the stock screen brightness buttons do not work (yet). A script and a service file (which are both available via the asus-screen-brightness AUR package) have to be used to allow users to change the brightness via the script. The problem is, with that service enabled, it only succeeds sometimes. About have of the time booting the laptop it fails, most likely because the necessary nodes in /sys/ do not exist yet. Restarting the service manually after booting does the trick:
[root@tachychineta shapeshifter]# sc status asus-screen-brightness
asus-screen-brightness.service - Allow user access to screen brightness
Loaded: loaded (/etc/systemd/system/asus-screen-brightness.service; enabled)
Active: active (exited) since Fri, 12 Oct 2012 11:23:44 +0200; 1min 1s ago
Process: 320 ExecStart=/usr/bin/asus-screen-brightness allowusers (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/asus-screen-brightness.service
Oct 12 11:23:44 tachychineta systemd[1]: Starting Allow user access to screen brightness...
Oct 12 11:23:44 tachychineta sudo[349]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/chmod g+w /sys/class/backlight/intel_backlight/brightness
Oct 12 11:23:44 tachychineta sudo[349]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: cat: /sys/class/backlight/intel_backlight/max_brightness: No such file or directory
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: /usr/bin/asus-screen-brightness: line 8: /10: syntax error: operand expected (error token is "/10")
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: /usr/bin/asus-screen-brightness: line 10: 2*: syntax error: operand expected (error token is "*")
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: cat: /sys/class/backlight/intel_backlight/brightness: No such file or directory
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: chgrp: cannot access ‘/sys/class/backlight/intel_backlight/brightness’: No such file or directory
Oct 12 11:23:44 tachychineta asus-screen-brightness[320]: chmod: cannot access ‘/sys/class/backlight/intel_backlight/brightness’: No such file or directory
Oct 12 11:23:44 tachychineta systemd[1]: Started Allow user access to screen brightness.
[root@tachychineta shapeshifter]# sc restart asus-screen-brightness
[root@tachychineta shapeshifter]# sc status asus-screen-brightness
asus-screen-brightness.service - Allow user access to screen brightness
Loaded: loaded (/etc/systemd/system/asus-screen-brightness.service; enabled)
Active: active (exited) since Fri, 12 Oct 2012 11:25:28 +0200; 2s ago
Process: 2547 ExecStop=/usr/bin/asus-screen-brightness disallowusers (code=exited, status=0/SUCCESS)
Process: 2579 ExecStart=/usr/bin/asus-screen-brightness allowusers (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/asus-screen-brightness.service
Oct 12 11:25:28 tachychineta systemd[1]: Starting Allow user access to screen brightness...
Oct 12 11:25:28 tachychineta sudo[2593]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/chgrp users /sys/class/backlight/intel_backlight/brightness
Oct 12 11:25:28 tachychineta sudo[2593]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 12 11:25:28 tachychineta sudo[2597]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/chmod g+w /sys/class/backlight/intel_backlight/brightness
Oct 12 11:25:28 tachychineta sudo[2597]: pam_unix(sudo:session): session opened for user root by (uid=0)
Oct 12 11:25:28 tachychineta systemd[1]: Started Allow user access to screen brightness.
Exactly the same problem occurs with asus-kbd-backlight.service which is needed to allow users to control the keyboard backlight. It also fails because of missing /sys/ entries if started too early.
Problem 2: automatic login & X11
I use the method described on the wiki to autologin into TTY1 with my user and my .bash_profile contains
[[ $(fgconsole) = 1 ]] && startx
and my .xserverrc is configured as explained in this fantastically useful article by falconindy.
This way, X starts automatically and my session is properly authenticated for things like udiskie. I'm not using [testing] but instead rebuilt polkit with --enable-systemd and it's working just fine. The problem is, just like in problem 1, Xorg fails to start every now and then, failing with
(EE) No devices detected.
I don't have a full log because it hasn't happened in a while, but I'm very certain it's because the chipset isn't ready, yet.
Solutions?
I added "i915" to /etc/modules-load.d/static.conf hoping that would cover both the Xorg and backlight problems but it doesn't help. I then tried adding i915 to my MODULES in mkinitcpio.conf and rebuilding the initramfs and at least it looked like that way the problems went away but it added about 4 seconds to the time spent by the "kernel" during boot which is quite unacceptable. (Plots with and without i915 in MODULES).
I read the systemd.unit and systemd.service man pages but I can't find a way to speficy required kernel modules for a service file. I'm not sure if specifying the modules in /etc/modules-load.d shouldn't be enough (because apparently it's supposed to load for sysinit.target, which is early) but apparently it isn't.
Any ideas how I can get these services to work properly without sacrificing too much boot time?
Thank you
Last edited by Shapeshifter (2012-10-12 10:20:09)

Please fill a bug report.

How can I get Time Machine to back up an external hard drive (iPhotos) that is attached to airport extreme base station. Note: Time machine is usb to macbook pro and external drive with iphotos is usb to airport extreme base station. Help please. Thanks!

How can I get Time Machine to back up an external hard drive (iPhotos) that is attached to airport extreme base station. Note: Time machine is usb to macbook pro and external drive with iphotos is usb to airport extreme base station. Help please. Thanks!

Once you have the drive connected to your Mac, click System Preferences (gear icon) on the dock
Click Time Machine
Click Options
Be default, the hard drive will be Excluded from backups. Click the drive to highlight it, then click the "-" (minus) button at the bottom of the list to remove the drive from Excluded items.
The drive will be backed up on the next Time Machine pass
Everything above assumes that the hard drive has been formatted in Mac OS Extended (Journaled) as Time Machine will only backup drives in that format.

Suppose I have two identical laptops loaded with my current time machine back up. I take one on a trip and update it with time machine but leave it. I come back w time machine HD and connect the home laptop, will it just update or start over from scratch?

Suppose I have two identical laptops loaded with my current time machine back up. I take one on a trip and update it with time machine but leave it behind. I come back with the time machine HD and connect it to the home laptop, will it just update or start over from scratch? is there a way to make it just update it?

You might have better luck using a clone.
Clone - Carbon Copy Cloner (Often recommended as it has more features than some others)
Clone – Data Backup
Clone – Deja Vu
Clone - SuperDuper
Clone - Synk
Clone Software – 6 Applications Tested
Commonly Used Backup Methods

Where are my photos? just tried to access time capsule after my first back up and am unable to open iphoto to verify they were backed up.

where are my photos? just tried to access time capsule after my first back up and am unable to open iphoto to verify they were backed up.

You can't open your backups directly with apps.
But you can see some types of files in your backups. If you're still on Snow Leopard (or Lion with iPhoto '09 or earlier), see the gray box at the end of Time Machine - Frequently Asked Question #15.
If you're on Lion with iPhoto '11, you can use the Finder to see the iPhoto library, per the beginning of that same link. All you can see there is the library and size.

Can I do a fresh install of os x to new SSD and restore applications with time machine?

I am upgrading to a new ssd. I have my current system backed up with time machine. Can I install/format (extended journaled) and then recover my time-machine stored application to my new ssd?

"BTW, you should NEVER use the Finder to copy items from TimeMachine. Use the TimeMachine application to recover files and applications."
I don't know how to use the finder to copy files. I am assuming I will be propted to use the TimeMachine application as a part of the clean install from snow leopard ( I am not upgrading to lion as of yet...). I will have my mac os x disk, time machine partition on a seperate external hard drive, BlacX 2.5/3.5 HDD usb docking station and new blank crucial m4 ssd at my avail. save for my wits...

HT201250 my time capsule is taking too much time indexing backup and then taking longer time to back up ( 207 days ) or longer !!! what shall i do ?

my time capsule is taking too much time indexing backup and then taking longer time to back up ( 207 days ) or longer !!! what shall i do ?

Try 10.7.5 supplemental update.
This update seems to have solved this problem for many.
Best.

I bought a new mac and i migrate with time machine...but the backup was a little bit old and weren't save the latest modify i made in my website.. is it possible take the uploded site in iweb? sorry but i don't speak english very well.

I bought a new mac and i migrate with time machine...but the backup was a little bit old and weren't save the latest modify i made in my website.. is it possible take the uploded site in iweb? sorry but i don't speak english very well

But what can I cut and paste? the html code or image and text directly?
depend on which template you used.
if you use iweb photos page template then you need to search for my photos page solutions in this forum.
@ot: cut and paste from the online version
@rw: You can drag an image from the website to the Desktop
have your try your methods in iweb photos page?

My Time Capsule has stopped backing up. I have an Apple Time Capsule which backs up by wireless. For the last 3 days it has not backed up. I get this message: "The backup was not performed because an error occurred while copying files to the backup disk.

My Time Capsule has stopped backing up.
I have an Apple Time Capsule which backs up by wireless. For the last 3 days it has not backed up. I get this message:
"The backup was not performed because an error occurred while copying files to the backup disk."
I have gone into Mac Help and followed this down to stage 4:
under shared it lists my time capsule and my husband's iMac - both use the time machine but we have switched his off temporarily. Clicking on my Time capsule I get "Connected" and "Sharepoint" - I didn't have to enter connect or password
I don't understand stage 5: how and where do I select the disk or volume that contains Time Machine backups ? How do I know which it is? My disk utility lists 160.04 TOSHIBA MK... with sub-heading Macintosh HD. It also lists (with a "CD" icon) HL-DT-ST DVDRW GS22N
Under stage 6, how and where do I Locate your backup ? I try dragging my Time capsule from Finder to the Disk Utility side panel but it won't go. What is my computer's name?
Please someone help! I'm completely stumped.
Thanks,
Maggie
Mac Help says:
If you back up to a Time Capsule or network disk:
Open the Time Machine pane of System Preferences, and slide the switch to Off.
Open Time Machine preferences
Open Disk Utility, which is in the Utilities folder in the Applications folder.
Open Disk Utility
Make sure the Time Capsule or network disk is turned on and available.
Open a Finder window, select your Time Capsule or network disk in the Shared section of the sidebar, and click Connect. If necessary, enter your user name and password.
On the Time Capsule or network disk, select the disk or volume that contains Time Machine backups. Depending on how your Time Capsule is set up, there may be one or more disks or volumes.
Locate your backup, and drag it to the Disk Utility sidebar.You can identify your backup by looking for your computer’s name in the backup’s filename.

Hello,
Thanks to the great Pondini...
http://pondini.org/TM/C3.html

Can anyone help me?Time Machine couldn't complete the backup to... An error occurred while copying files. The problem may be temporary. If the problem persists, use Disk Utility to repair your backup disk. What is the problem? I've made no changes.

I recently starting receiving the error message "Time Machine couldn't complete the backup to... An erro occurred while copying files. The problem may be temporary. If the problem persists, use Disk Utility to repair your backup disk. I have had no problems backing up my MacBook Pro 2011 to my Western Digital My Book Live through a Linksys EA4500 router until recently. I've made no major changes. I've ran a diagnosis on my back up drive with no problems. The Time Machine back up starts, but about after about 5 to 10 minutes I get the error message. I can see the shared drive in Finder. The light on the drive blinks while it starts the back up. I can see the shared folders on the networked drive. The backup process starts but for some reason it just stops. Can anyone help?

You can't repair a network volume in Disk Utility.
Backing up to a third-party NAS with Time Machine is risky, and unacceptably risky if it's your only backup. I know this isn't the answer you want, and I also know that the manufacturer says the device will work with Time Machine, and that it usually seems to work. Except when you try to restore, and find that you can't.
If you want network backup with Time Machine, use as the destination either an Apple Time Capsule or an external hard drive connected to another Mac or to an 802.11ac AirPort base station. Only the 802.11ac base stations support Time Machine, not any older model.
If you're determined to keep using the NAS for backup, your only recourse for any problems that result is to the manufacturer (which will blame Apple.)

Time Machine reporting "The backup was not performed because an error occurred while copying files to the backup disk". Anyone have any idea what's gone wrong?

After months of working OK Time Machine is reporting "The backup was not performed because an error occurred while copying files to the backup disk". Anyone have any idea what's gone wrong?

asknrobson wrote:
Wierd!
I followed #C3 and loaded Time Machine Buddy, which was defnitely helpful, then deleted the file that the backup failed at, but after 3 more attempts I stopped deleting or excluding files as this wasn't improving the situation.
The recommendation is to exclude those files from being backed-up, not to delete them!
Updating boot support partitions for the volume as required:
Yes, that's a bit misleading. It just means that will be done, if it's required, which it isn't on your backups.
I have no idea if anything actually was changed however just when I had given up and walked away, TM has started working after a week of failing.
It probably did find and fix something. Just for reference, Disk Utiltiy usually shows the progress and repair messages in the center part of the window, but often doesn't when repairing a sparse bundle on a network. You can see the messages at any time by clicking the Log icon in the toolbar, or select Window > Show Log from the menubar.
Anyway, glad it's sorted out!

Interclue fails to initalise upon restart from either shut down or back out of hibernation. Works when re-installed, but then fails every time.

Interclue fails to initialize upon restart from either shut down or back out of hibernation. Works when re-installed, but then fails every time. What would cause this situation. Never had problems with this add-on with Firefox until I downloaded Firefox 4.0. I can disable, re-start, enable,re-start, and it works fine. The same scenario holds true if I uninstall and then re-install add-on.

Just a guess, but I wonder if you have some application or process hanging up that's stopping it from shutting down? You might try closing each application individually and see if this helps.
Good luck!

Users contacts missing after failing over and then failing back pool

We have 2 Lync enterprise pools that are paired.
3 days ago, I failed the central management store, and all users from pool01 to pool02.
This morning, I failed the CMS and all users back from pool02 to pool01.
All users signed back in to Lync and no issues were reported. A user then contacted me to say that his contact list was empty.
I had him sign out and back in to Lync, and also had him sign into Lync from a different workstation, as well as his mobile device. All of which showed his contacts list as empty.
We have unified contacts enabled (Hybrid mode with Office 365 exchange online, and Lync on prem). When I check the users Outlook contacts, I can see all of his contacts listed under "Lync Contacts", along with the current presence of each user.
If I perform an export-csuserdata for that user's userdata, the XML file contained within the ZIP file shows the contacts that he is missing.
I've also checked the client log on the workstation too, and can see that Lync can see the contacts as it lists them in the log. They do not appear in the Lync client though.
Environment details:
Lync 2013 - 2 enterprise pools running the latest December 2014 CU updates.
Lync 2013 clients - running on Windows 8.1. User who is experiencing the issue is running client version 15.0.4675.1000 (32 bit)
I have attempted to re-import the user data using both import-csuserdata (and restarting the front end services) and update-csuserdata. Both of these have had no effect.

Hi Eason,
Thanks for your reply. I've doubled checked and can confirm that only one policy exists, which enables it globally.
I believe this problem relates to issues that always seem to happen when ever our primary pool is failed over to the backup pool, and then failed back.
What I often see is that upon pool failback, things like response group announcements don't play on inbound calls (white noise is heard, followed by the call disconnecting), and agents somehow get signed out of queues (although they appear to be signed in to
the queue when checking their Response Group settings in their Lync client. I've also noticed that every time we fail back, a different user will come to me and report that either their entire contacts list is missing, or that half of their contacts are missing.
I am able to restore these from backup though.
This appears to happen regardless of if the failover to the backup pool is due to a disaster, or to simply perform pool maintenance on our primary pool.

Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem." Tried suggestions I've seen on the forum.

Similar Messages

Maybe you are looking for