13 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHSudden a/c malfunction
Leading reported evidence
Check fuses a second time
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Leading evidence: 'Check fuses a second time' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check fuses a second time' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
You will have to disconnect switches (remember which go where) from the back side of these two panels so the horseshoe will slide out.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion
I'd rather have to replace the ignition switch than deal with a new AC compressor.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
13 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T090147Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I read the manual (no help there), checked the fuses (all were in order) and I have seen no mysterious puddles under the car (an '03 996). The a/c worked fine when I last drove the car (Wednesday) but this morning (Sunday) - zippo. Any suggestions before I have to go see the dreaded service department (it's under warranty, so that's ok)?
Thanks in advance.
By the way, I did do a search, but didn't see any relevant threads - not that there might not be any - please feel free to direct me to them if they are out there.
Pull the two panels off surrounding the stereo (just get you fingers under and pull towards you) and remove the retaining screws around the horseshoe panel; I think there is 4 of them. You will have to disconnect switches (remember which go where) from the back side of these two panels so the horseshoe will slide out. Slide the entire assembly unit out and see if the loom going into the A/C control unit is fully engaged. If it is, it either died or is not getting power to it I would venture to guess.
It's the ignition switch. In Acc mode, all is well. With the engine on, zippo power to the fan OR the wiper blades. Danny - a service advisor at Champion diagnosed it instantly over the phone and had me confirm it via the wiper on/off test. A good guy indeed. (But I still won't let them wash the car)
Thankfully we're CPO.
I was going to mention the ignition switch (no really, I was!) but I thought I might get laughed off the forum. Next time, I'll just bear the "slings and arrows" and go with what my gut tells me.
I'm glad it was something relative small and inexpensive.
Tim,
I believe you.
I actually saw a thread on a Mercedes forum that suggested this was an ignition problem, then the service advisor confirmed it. Must be a German thing. And yes, I agree that an ignition switch is a much better option than an a/c compressor, even if it is a warranty issue (I want the car back ASAP)
This is a source reference. Confirm exact model applicability in the original material.
