Massive bugs in ARD 3.7

So I use ARD on a daily basis at work to manage over 300-400 users, and before this update everything was working fine.
The major issues that the 3.7 update seem to have caused are the following:
Eats up huge amount of RAM which cause the whole machine to crash and force quit will not work at all!!
Keeps trying to populate list of machines (even though a machine is found and authenticated it will disappear and reappear in a loop)
Failes/stuck on authenticate many machines that were working before
Not showing all users on network (even though they are there and working through normal VNC)
Showing users as OFFLINE even though they are ONLINE (if you connect to them it will authenticate and connect but not change status to online)
Copy/Install/Unix commands keeps giving failure error and will only work if you keep trying a couple of time
Will not identify machines through their DNS so all created saved lists are instead listed by IP obviously causing a problem as we use DHCP so lists are useless the next day..
All users on network have updated ARD to 3.7 and most of them run 10.8.5
The admin machine run ARD 3.7 with 10.9 on a 2010 iMac with 8GB RAM
Steps taken to fix problems with ARD, non of which solved anything:
Trashed container preferences and rebuild ARD from scratch with fresh install
rebuild machine with a brand new 10.9 install
Tried setup on a different machine (MacBook Retina with 16GB RAM)
Apple need to sort this out asap as ARD is now completely unworkable and just a nightmare when trying to support users.. Instead we are back to asking IP of user and using screen sharing through VNC (finder) instead..
Anyone have any information about any updates that will fix this? I have read about that they plan a 3.7.1 update but no ETA and not what bugs it will fix.

Good, so basicly you rely on the backup computer as you don't have any dedicated test computer. I guess you refer to the iMac as your admin computer now because as things are cleared it will eventually become the ”production environment”. I use that strategy aswell sometimes so I would back you up but I'd be clear on the naming - that's your test computer. Your backup computer is part of the production system thus should have both that treatment and credit.
I know this problem only arise in larger networks but in pre 10.9 environment that's just one 5 min downgrade so it shouldn't be a problem even though you did the untested upgrade on your mainframe. The ARD client is of no concern (this time at least) so there is no deploy issue.
It's only when OSX 10.9.0 and ARD 3.7.0 admin meet you have a real problem as you are on thin ice downgrading. If that's a test fleet it wouldn't be of any concern but if that's someting you rely on I'd definately say that the largest problem is the strategy of the admins. Two .0 mistakes in an important computer is a system error and that strategy is a ticking bomb.
I mean when software is proven fine on the test fleet the next step should be to put it on non important computers. Those are the ones nobody depends on and I was now talking about 10.9 in particular. Home computers are good because you get well exposed of them and your also have close relationship with the users who will not be afraid to give you the slightest flaw right in your face.
3.7.1 seams better as the computers doesn't flip around (so far) but the IP:s are still strange.
ifconfig the client and it will tell you what you see in 3.6.x but what you read in 3.7.1 admin is still fantasy. At least you adress the correct computer sending unix commands or want to monitor/control it even though the IP is wrong. Too early to tell but that's what I have found during the first day.

Similar Messages

Lightroom 4: Massive BUG with White Balance / Quick Develop. Totally Unreliable!

I just recently updated from LR3 and just now found a massive bug concerning the white balance adjustments in the quick develop module.
After a studio shooting and especially after weddings I use the "make warmer" adjustment in the quick develop panel to give all (a few thousand NEFs) a nicer look all at once.
The great thing about this is - like all quick developments - that it increases the color temperature relative to each image's starting white balance.
Yesterday I wanted to edit my first wedding in LR4 and like in LR3 applied one click "make warmer" to all images at once (previously WB was "as shot").
While I browsed through the images to rate them I noticed some of them were very "pinkish".
After closer inspection it came out that a lot of images (50%-60%) had the following custom WB set: 5316, Tint: +10.
It is always this exact combination no matter what the "as shot" WB was.
That setting of course applies way too much magenta to a lot of images.
After resetting the WB of single images to "as shot" and selecting "make warmer" once again the images look fine and get appropriate WB values.
But every time I select more than one image to apply "make warmer" a lot of them get the strange value of 5316 and +10.
Sometimes it's even just the first few images of the selection that get correct values and all the following ones get the off value. It appears to be totally random.
I tried completely resetting all images prior to "make warmer", setting them to different camera profiles first and even switched them to Process 2010 again. But absolutely no luck! :-(
The "make warmer" tool gives me totally unusable results.
I find it strange, that I couldn't find anything about that on the net.
PLEASE fix this ASAP.
To apply WB to thousands of images individually is a real pain.
I would be glad to support you fixing the issue.
My setup:
Nikon D700
Nikon D300s
(Both cameras affected, I only shoot NEF)
Win7 x64
LR4.1 as well as LR4.2 RC

@ssprengel
I get your point but that is exactly my problem.
Not only is there no pattern but also once I reset a file that got 5316+10 to "as shot" and select "make warmer" for it again it does get the correct value! As long as I select it as a single file without others.
So just to simplify my findings and explain what I have been doing all night:
- SELECT 5 files in Library View (all freshly imported, no settings altered, WB "as shot")
File 1: 5700 / -8
File 2: 5500 / -8
File 3: 5550 / -8
File 4: 5450 / -6
File 5: 5500 / -7
- CLICK "make warmer" once
Result:
File 1: 6089 / -8
File 2: 5867 / -8
File 3: 5316 / +10
File 4: 5316 / +10
File 5: 5316 / +10
1 and 2 are okay!
- SELECT 3-5
- RESET THEM
Result:
File 3: 5550 / -8
File 4: 5450 / -6
File 5: 5500 / -7
- CLICK "make warmer" again
Result:
File 3: 5316 / +10
File 4: 5812 / -6
File 5: 5867 / -7
File 4 and 5 are okay!
- SELECT File 3 again
- RESET IT
- CLICK "make warmer"
Result:
File 3: 5923 / -8
now File 3 is okay, too.
It is completely random!
But that is no way to work, of course.
I have two weddings from last week and am going nuts already.

Long standing bug in ARD

There is a LONG STANDING bug in ARD dating back to at least v2.0, maybe earlier.
While controlling a remote Mac, for seemingly no reason, the display stops refreshing. The connection has not been lost just refresh is stopped. A single refresh workaround is to click the color adjustment bar, no need to move it, just click it and you get one refresh. This happens to me way too frequently! It occurs on PPC as well as Intel Macs, on local LANs and over the Internet through VPNs.
Sometimes you can break out of this by closing the connection and connecting again but it usually requires the remote machine to restart the ARD service. Doing this with ARD itself usually leaves the remote machine unreachable (ARD service stopped.) I have taken to using a near by Windows machine then ssh'ing into the Mac to manually restart the service. This works but the refresh problem re-occurs after an undetermined amount of time.
There seems to be no clues as to why this happens. There is never any particular task I am performing, no specific app I am always running, etc, etc.
Excuse me if this has already been brought up and if someone knows a fix or can point me to a KB article I would be most appreciative!
Thanks,
Josh
G3, G4, G5, Intel iMac, you name... Mac OS X (10.4.6) Mac OS X (10.4.6)

I, too have experienced this problem. However, much more so since I upgraded to ARD 3. This can happen, as you say, on a wide variety of clients: eMacs, G5 Dual, iMac G5, Powerbooks. Most annoying. I have found that if I use TB2 to control the client, I will find, in some cases, the SystemUIServer process is hung. By Force Quitting this process and Re-Starting the client, I am able to get ARD to run again.
This seems a little more severe than your problem, but I have had the same experience as you describe as well--the SystemUIServer is not hung in these cases. I can generally find nothing wrong on the client to account for the behavior.
Nor have I found a satisfactory answer to the problem on this forum. Would love it someone could offer a clue!
PowerBook G4 Aluminum 15 Mac OS X (10.4.6)

Massive bug in Sonic the Hedgehog -or is it just me?-

I've got a 5th gen iPod and I was very excited by the announcement of Sonic the Hedgehog for it to while away the long train journeys! However, there appears to be a massive and crippling bug that means I can't get 10 seconds into a game.... I think i've traced it down:
Holding the down button (the play/pause of the click wheel) for a longish time will cause the game to freeze, and then Sonic will quit, returning me to the games menu.
I'd be interested for others to confirm this bug, because it'd be nice to know that it's not just me, and that Apple is aware of it. Perhaps the bug is because holding play/pause normally turns off the iPod?

On my 3rd gen Nano, holding down the "down" button (ie the play/pause button) actually goes one further, and turns OFF the ipod - in the middle of a game! I'm training myself to just touch the play/pause to look down, or to spin, but it's hard! Still have the muscle memory or whatever from my Megadrive from years ago. It's also incredibly hard at the moment to switch thumbs for jumping. On the old Megadrive controller your left thumb would control direction and your right thumb would jump. On the tiny nano click wheel, you need to switch which thumb makes you jump according to which direction you're going in...if you're running right, your LEFT thumb has to be used to make you jump: frustrating. I've tried the B control scheme but find A generally better. And the game is still fun though!

ITunes 7.5 Massive Bug

Today I upgraded my iTunes 7.3 to 7.5. Yesterday everything was fine...but now whenever I try to open iTunes...it just hangs! And I've to end that program from 'Task manager'. I'm using Windows XP Sp2. I tried several uninstallation and reinstallation...but nothing seems to work! Even when I tried to roll back to 7.3...it says it can't read my library as that iTunes library was made by a newer version of iTunes (i.e. 7.5). Please help guys...looks like a major bug to be fixed in **** iTunes !

This might actually be an issue with your firewall and/or anti-virus software. I'm using 7.5 and don't have any issues with it, and I'm also on XP SP2. Did you try closing your firewall and/or anti-virus programs before opening iTunes? You might find that another program was interfering because it thought 7.5 was a new unauthorized program - I think this might esp be true for Norton users.
However, if you want to go back to 7.3 I can help you restore your old library:
1. Uninstall 7.5 and reinstall 7.3 but don't try to open it yet.
2. Go to My Music>iTunes>Previous iTunes Libraries. You should see a file called 'iTunes Library 2007-11-11' (or dated whenever you upgraded). Copy this file into the 'iTunes' folder in your 'My Music' folder.
3. Open the iTunes folder and move the 'iTunes Library.itl' file onto your desktop. Rename the file you just copied to 'iTunes Library.itl'.
4. Open the 7.3 version - it should look just like it did before!
If this worked you can delete the 'iTunes Library.itl' you moved onto the desktop; if it didn't you'll need to close iTunes, move that file back into the iTunes folder and go back to trying something else with 7.5. The only reason it might not work is because you've reinstalled several times.

Massive bug by combining Shadow/Highlight and a cross fade

Hi. I found what appears to be a bug by using a cross fade between two clips with the shadow highlight effect. I cross faded two clips (240fps AVCHD from FS700) each with RGB Curves and Shadow/Highlight and sometimes I get this nasty side effect. The side effect is a random white flashing, or rather an erratic application of the shadow/highlight effect. Maybe it's because it is trying to process the effect on footage which is slowly losing opacity due to the cross fade, and as this happens, the colour data changes as a result. This effect may not happen outright when you try it, I think it applies to specific clips, or clips where the shadow number is higher than the highlights or vice versa. It is now happening again in my new edit and this worries me because I like the effect that it gives, but not the buggy side effect.
Here is the video where I first experienced it. It only appears to happen at 2:18, but now in my next video, it's happening in my opening shot.
Rendering with gtx570 & pprocs6.

The problem occurs when two clips that both have Shadow/Highlight adjusment with different values are crossfaded. You get this light dark bands of flickering in the crossfade. It looks horrible.
SOMETIMES, disabling GPU acceleration works. Not always.
Setting the clipping amounts to 0, as opposed to the default of .01 will help with the clip flickering, but NOT the crossfade flikering. It will not help
Using Opacity keyframes as opposed to the Crossfade Video Transition Effect will not help.
The only sure way to solve the problem is to make INTER clips. Render the two clips seperately with all shadow/highlight effects, then replace the clips on your timeline with the rendered clips and THEN crossfade them.
Also, for those of you that simply notice the "sky" in your scenes flickering when using Shadow/Highlight Adjustment, make sure to set at least the Black Clip from .01 to 0. This will stop that annoying flicker throughout the entire clip.

File sharing between rMBP and iMac massive bugs.

I recieved my new rMBP this week to replace my Macbook Air and join my iMac and Mac mini and immediately came across a problem.
Ive always had file sharing enabled on all computers and sent and recieved files to the iMac from the Macbook Air with ease.
However I tried to copy a file from the iMac to my rMBP and was provided with an error code (-8000 something) and was forced to relaunch finder.
I brought the Macbook Air back up (incidently I used migration assistant to copy files and settings over from MBA) and it was able to send and recieve files from iMac with no problems.
The first thing I notice is that the rMBP asks for an admin password to write to the iMac - the MBA doesn't. If I check permission settings on folders from the iMac from both machines they both have the same permissions set so I can't understand this.
Now the error code when trying to copy from rMBP to iMac doesn't appear - instead I send a file and Finder goes crazy and copies a 0 byte file with the same file name onto the iMac thousands of times until I force Finder to relaunch again.
Incidently I can send files to and from the Mac Mini without any issues - and I can as of now recieve files from the iMac ok, but not send to.
Its a very odd bug, ive tried repairing permissions on both machines and restarting both but ot no avail. Can anyone think of anything to delete/reset/try to fix this odd behavour?

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Step 1 should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary, and if everything is working as expected after step 1.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Massive bug after 10.3 update on Z10

Hi all and thanks for the forum.
I've been experiencing annoying trouble after updating my Z10 BlackBerry to 10.3 OS last night. Basically:
- The phone seems running fine, it starts an I can switch between the application panels, but-
- Not one application starts. I mean, I can click the application, then the device switches to the "zero" application panel - the one meant to show the opened applications - but this one stays empty. Which is rare by the way because, at least in the previous version of the OS, this panel wasn't even accessible when there was no app running.
To explain further on the symptoms:
- The initialization of the phone is really long - more than 10 minutes - and it seems to be installing the updates every time I start it, even after various resets.
- The Rapid Access Bar - for setting up brilliance, sounds, blocking rotation etc. - works fine, except for accessing the Configuration app.
- The Camera and the Research function don't work, same as the other apps.
- The Hub is accessible but empty.
- The one app that does start is the Phone. This one does works fine, I can make and receive calls and access the basic contact list in it, but cannot reach the detailed contact information since that action calls the Contacts app.
- Connecting my device to a PC with an USB link, the device isn't detected. It does charge but I cannot access the data either through Windows Explorer or BlackBerry Link. BlackBerry Link does start automatically and I keep on hearing my PC ring tone for connecting and deconnecting an external device, frequently and irregularly.
- It occurred once, at starting my phone while it was linked to the PC, that it was detected by BlackBerry Link. But even that time it couldn't acces files nor start any backup.
- Note that the OS starts on the empty "0" panel. On the ancient OS version it used to start on the n°1 app panel.
Does anyone ever experienced that situation at upgrading his OS or would have an idea on how to solve it? My paramount point is to save the files I have on the device, media most of all and app data if possible. That excudes reinitializing, which is the only option offered by BlackBerry Link at not detecting the device. Note that I do not have an SD card and everything is stored in the internal memory.
Do other sowtfares exist that would enable me to reach the data stored on my phone? Or would it be possible to downgrade the OS version without risking losing the data?
Many thanks in advance.
Julien
PS: Although I doubt that it has anything to do with that, my service provider is Entel in Chile.

Hi all,
I figured out my problem is exactly the same as that person's: https://supportforums.blackberry.com/t5/BlackBerry-Z10/All-apps-won-t-work/td-p/2572409
He solved it by doing an entire software reset and wasn't able to save his pictures, though...
I think all that's left to me is technical support and praying that they won't erase the data.
Until then any help on the matter will still be appreciated.
Cheers.

Massive Bug - Will Not Allow User to Cancel Pro Se...

Dear Skype (Microsoft?),
https://www.facebook.com/photo.php?v=10151759268201397 - watch that video.
You need to fire the guy/gal who is in charge of the Cancel button - which will not let you cancel and causes your users to continue to incur charges.
Oh, and you owe me $3.

Welcome to Apple Support Communities
The external drive is formatted in NTFS. OS X can't write in NTFS disks.
You have different options, but the easiest is to install an application ilke Paragon NTFS. This app will allow you to copy your iTunes library to your external drive.
Another option is to format your external drive in a format that a PC and a Mac can write in. In this case, you can format it in exFAT or FAT32, and I suggest you FAT32 because I doubt you have files bigger than 4 GB in your iTunes library. If you have them, you will have to use exFAT, and you will have to format the external drive on a PC

ITunes update Massive bugs, POS

How do I submit a complaint to Apple about the latest version of iTunes. It is buggy as all ****, even worse than pervious iTunes which is bad, but now it keeps erasing my iPhone 4s every time I plug it in to my computer.

Well, you found these forums, certainly you are intelligent enough to find the "Contact Us" link at the bottom of every Apple web page and the feedback pages.

Massive Roaming Bug

I and two of my friends have just arrived in New York. We all have O2 3G iPhones running the latest software. The 3 phones were purchased in the UK from different stores at different times.
ALL 3 phones are exhibiting the same massive bug as follows.....
For the first day or so we were here all phones worked as normal whilst connected to the roaming network AT&T.
Today, all of the phones now connect to T-Mobile (with no way of changing that).
The T-Mobile signal strength if 100% for 10 seconds, then 0% for 20 seconds, then back and forth for ever.
You cannot, call out or in and text messaging fails.
After 5 mins or so the phone auto-reboots and the cycle continues.
Manually re-booting does not fix the problem.
I cannot got off the T-Mobile network.
My phone is 100% totally useless. I can do nothing with it whatsoever.
All of the phones are exhibiting the same problem.
Went to the NY Apple Store and they said they could not help because it was a UK phone.
Went to AT&T and they just laughed saying the iPhone is causing nothing but problems and other roaming customers have reported the same problems. After spending 30 minutes with them I left the store with the same problem.
Sine 3 phones are all doing this (and I have 1 other UK friend here with an iPhone and his phone is working normally, however, this is his 3rd phone as the other 2 did exactly this issue as well).
This is totally unacceptable and bugs like this should not make it into production devices.
I travel abroad all of the time and the iPhone has never presented these problems. Here in NY and 3 out of 4 phones are bust.

This is not a roaming bug. All GSM cellphones will choose the strongest tower available to use for voice and data. By default all GSM phones are set by the manufacturer to auto-detect any GSM carrier tower for better reception though unfortunately this can cause roaming charges to be incurred. Due to the USA has several GSM carriers (top two are AT&T and T-Mobile) with towers in close proximity to one another you can change the iPhone 3G network settings to only use one specific carrier by going into "Settings" then "Carrier" then select which network carrier you want to use. This can be very handy for those living close to the USA/Canada boarder where they may be picked up by the other country carrier network. Keep in mind that by setting the iPhone to only use one carrier you do run the risk of dropped calls when roaming outside that specific carrier's network coverage. Though at least you won't see roaming charges Note: When roaming in the USA I leave my network settings to auto and when I get back home my Rogers invoice shows the dates and times I was roaming on either AT&T or T-Mobile. I've never had any issue when roaming in the USA of being billed by both carriers at the same time when placing a call due to as stated the iPhone will pick the strongest signal.

ICal and Addressbook connecting to eGroupware - various bugs?

Hi all,
given CalDAV and CardDAV as standardized protocols, it shouldn't be too much of a problem to connect to private calendar and addressbook servers, you'd think... For some year's I'm running a eGroupware server, and while this product is far from being bug free, I believe it's basically massive bugs in Apple's Ca*DAV protocols that keep the synchronization from working. Let's start with iCal:
Originally, eGroupware's CalDAV implementation returned fully qualified URIs (like https://www.example.com/egroupware/calendar/) for all kinds of properties, e.g. calendar-home-set. As a result, iCal sent requests with the path //www.example.com/egroupware/calendar - i.e. instead of properly parsing the URI, it just stripped off the protocoll indicator and tried to treat the remaining string as a path.
As the CalDAV standard doesn't make any hint if URIs should be supplied as fully qualified or relative URIs, returning full URIs seems to be the safer bet, and iCal's reaction on this is IMHO as clearly a bug as it can be. Nevertheless, I patched eGroupware to supply relative URIs, and hey ho, iCal integrates fine with eGroupware now. By the way, eGroupware has some hard coded behaviour to supply only the events of one month back by default, but you can patch that behaviour as well, of course.
Now to Addressbook, and that's where I'm beyond my wits First of all, it is not possible to configure a CardDAV server in Addressbook itself, as the GUI is massively broken (just try to setup a CardDAV server https://www.example.com/egroupware/addressbook/ and you'll end up with a configured URL https://www.exmaple.com:443/egroupware/addressbook/:443<null> or something even more broken. You need to edit the file "Application Support/AddressBook/Sources/78E03291-22C9-4E27-9852-8480AD6A0F03/Configuration. plist" manually.
Now, still Addressbook sends a PROPFIND requst for current-user-privilege-set to /directory/ to the server. Don't know what kind of result the programmers expected from this, but on my CalDAV server nothing at all resides under that path, also it's not mentioned in the CalDAV as a general concept. After it got a 405 Method Not Allowed to this request, Addressbook continues sending more sensible requests, so it might not be an actual problem - I'm not sure.
Next is a PROPFIND query for addressbook-home-set to /egroupware/groupdav.php/addressbook/ wich is a perfectly expected behaviour from the standard. But first, the server replies with 401 Unauthorized. Addressbook then repeats the request, this time including the correct HTTP BASIC authentication information. Now, the server tries its best to handle this request according to standards. I quote the full response here, perhaps some pro spots a mistake in the response I'm to dumb to see:
HTTP/1.1 207 Multi-Status
Date: Sun, 06 Sep 2009 14:51:58 GMT
Server: Apache/2.2.12 (Debian)
X-Powered-By: PHP/5.2.10-2.2
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Expires: Thu, 19 Nov 1981 08:52:00 GMT
X-Dav-Powered-By: eGroupWare CalDAV/CardDAV/GroupDAV server
X-WebDAV-Status: 207 Multi-Status
Content-Length: 486
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Content-Type: text/xml; charset="utf-8"
<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:">
<D:response xmlns:ns0="urn:uuid:c2f41010-65b3-11d1-a29f-00aa00c14882/" xmlns:ns1="urn:ietf:params:xml:ns:carddav">
<D:href>/egroupware/groupdav.php/addressbook/</D:href>
<D:propstat>
<D:prop>
<ns1:addressbook-home-set><D:href>/egroupware/groupdav.php/addressbook/</D:href ></ns1:addressbook-home-set>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>
I read the CardDAV RFC over and over again, but this seems to be as correct a response as you could wish. Note: out of the box eGroupware doesn't generate the D:href sub-element to ns1:addressbook-home-set but directly puts the URI as content of that element. This is not correct according to the CardDAV standard, but iCal is ignoring exactly the same mistake of the CalDAV implementation of eGroupware. It doesn't make a difference for Addressbook either - both variants lead to the error message 'Von CardDAV-Server Fehler (207) für den Benutzer "xxx" erhalten.' This is a strange message to show, as 207 is not an error code. Of course I patched eGroupware to return 200 OK as HTTP status (contradicting the standard), and hey ho, in Konsole you'll see an error message stating "Expected multi-status response but got status code: 200".
So - Addressbook actually expects and checks for 207 Multi-Status, i.e. the message on the GUI is giving us no indication on the actual problem. Some easy checks proved that Addressbook wouldn't react any different if the server replies with plain nonsense (e.g. syntax errors in the XML file). So, obviously, Addressbook can't cope with an aspect of the response it gets, fails to generate any log or message box about the problem, and sets a misleading error indication on the GUI.
And now? Does anybody have a good hint what could Addressbook make work here? When can fixes to iCal and Addressbook realistically be expected, if at all?

Hello Pelzi,
Same problem here with iCal an eGroupware. Since I opgraded to SnowLeopard, my Calander isn't syncing anymore.
*iCal sends this:*
PROPFIND //192.168.3.199/egroupware/groupdav.php/calendar/ HTTP/1.1
Host: 192.168.3.199
User-Agent: DAVKit/4.0 (729); CalendarStore/4.0 (965); iCal/4.0 (1362); Mac OS X/10.6 (10A432)
Authorization: Basic ******
Depth: 1
Content-Type: text/xml
Content-Length: 143
Connection: keep-alive
<?xml version="1.0" encoding="utf-8"?>
<x0:propfind xmlns:x0="DAV:">
<x0:prop>
<x0:getetag/>
<x0:resourcetype/>
</x0:prop>
</x0:propfind>
*And Groupdav replies:*
HTTP/1.1 405 Method Not Allowed
Date: Mon, 07 Sep 2009 13:41:34 GMT
Server: Apache/2.2.3 (Linux/SUSE)
Vary: accept-language,accept-charset
Accept-Ranges: bytes
Keep-Alive: timeout=15, max=100
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
Content-Language: en
1e
<?xml version="1.0" encoding="
af
ISO-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<title>Method not allowed!</title>
<link rev="made" href="mailto:"[email protected]" />
<style type="text/css"><![CDATA[/*></style>
</head>
<body>
Method not allowed!
The
PROPFIND
method is not allowed for the requested URL.
If you think this is a server error, please contact
the webmaster.
If anyone has a solution?
Message was edited by: HansH8

Problems with ARD and headless MacMini (new 1,66 DualCore)

Hi,
i would like to set my brandnew MacMini 1,66 as webserver.
And there the problem starts: when the MacMini runs headless (without monitor attached) it thinks that there is a television attached and i get a very distorted screen when connecting via ARD 2.2. Attaching the DVI-VGA adapter does not help!
How can i tell the Mini to switch to a "normal" resolution without attaching a monitor?
I seems not to be very useful to connect a monitor to a computer that is supposed to run headless...
HELP!!!
1.66GHz Intel Core Duo processor Mac OS X (10.4.7) ARD 2.2

I have the exact same problem with two PowerMac G5's. I need to have full resolution on the remote G5 which has no monitor connected, but only get to choose between PAL and NTSC TV resolution. This is really annoying, and in my opinion a major bug in ARD 3.1 and below. Why is the user forced to see such a small remote window if the remote computer is capable of much more?

HUGE BUG IN Flash Player 9

I ran into this huge massive bug in FP9..
Reproduction steps:
1. Goto Flash Download page.
2. Select version 9 for Linux.
3. Install
This normally breaks down around step 2.

So its not a bug in the player .. its a problem in the
download of it.
Doesn't sounds like a massively huge bug in the player at
all.
>I ran into this huge massive bug in FP9..

Huge bug in messages in iOS6

Anyone noticed the massive bug in messages since iOS6? If you select any of your previous message threads that were there pre-update that show as coming from a name rather than a number, eg banking, companies, etc - the preview is there but then when you touch it to drill down it shows blank, go back and hey presto the entry has completely disappeared. Force close messages and it comes back - but only to do the same thing.
I don't think the messages are being cleared as they come back when you quit i think it is just a bug in showing the messages - but this really needs fixing quick!!!!
Pretty poor bug to introduce this really.
Edit: Actually already posted/spotted by other people https://discussions.apple.com/message/19635920#19635920
This needs fixing pronto!!!!!!!

Perhaps this is a stupid question, but I don't see anywhere that you said you saved the file anywhere. You just said you opened Pages, worked on a document for a while, then closed Pages. Did you ever, at any point, save the document you were working on to the desired folder on the external drive, or were you just expecting Pages to do that for you? If the latter, note that Pages cannot know where you want to save a file, and though it will do its best not to lose your changes to a document that has not yet been saved to a specific location, that document can only be saved temporarily to the system drive.
If you did save it to the external drive, but you either didn't see the document in that location at all when you got home or you saw it but it did not contain your changes, the only possibilities I see are user error or a serious problem with your system.
Also, note that you're getting some bad information here. The .DocumentRevisions-V100 is not stored on the "root drive" (whatever that is supposed to mean). It is stored at the root level of whatever drive the document in question is stored on, assuming that volume is formatted as HFS+. (If it isn't, there's a problem that applies to Versions, but not to the specific problem you have described. See Beware Lion’s Versions Bug on Network and Non-HFS+ Volumes.)
So, if the document has, in fact, been saved to the external drive, and that drive is not formatted as HFS+, then you will be unable to use Versions with that document, but autosave will still work just fine, and you should see your latest changes in the document regardless of where you are.

Massive bugs in ARD 3.7

Similar Messages

Maybe you are looking for