SSD Question

Timmy 2 toes · Saturday at 10:30 AM

I saw this message today, but what does it mean?
in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Thank you
TIMMY 2 TOES

FreeBooter · Saturday at 10:57 AM

Is this log from Even Viewer if so post the screenshot of the log at Event Viewer also post Event ID number.

Timmy 2 toes · Saturday at 11:46 AM

Levitate11 · Saturday at 12:43 PM

(When I saw your user name, I thought for a minute that the error code would be 867-5309. But then I realized it was Timmy 2 Toes, not Tommy Tutone. )

If you're up for a little grimy regedit and Component Services editing, this worked for me when I had an identical error (but with a different component).

1) You might want to google the specific CLSID in your error message and see if the instructions are different, but the error appears to be the same as the post below;
2) Do a System Restore "Create a Restore Point"
3) Edit CAREFULLY
4) Component Services is best found using the Windows Search Box

Link is below:
- Follow the instructions of tjnihal.
- When you go into the Component Services >...> DCOM area, right click and choose "View Details" to ease your pain
- When you add the "Local Service" in DCOM, be sure to type the space in the name. Click "Check Names" and it should come back with it in caps.

Local Activation permission issue - Windows Server / Windows update - Computer Repair

glasskuter · Saturday at 1:11 PM

Hi T2T. Dcom 10016 events are harmless and can be ignored. We all get them.

Ghot · Saturday at 1:13 PM

Yep. You can ignore 10016 errors.

gunrunnerjohn · Saturday at 1:37 PM

glasskuter said:
Hi T2T. Dcom 10016 events are harmless and can be ignored. We all get them.

I hope so, I see them quite often when I look at the event logs. AAMOF, there's so much crap in the event logs that it's hard to find real problem indications!

Ghot · Saturday at 1:41 PM

gunrunnerjohn said:
I hope so, I see them quite often when I look at the event logs. AAMOF, there's so much crap in the event logs that it's hard to find real problem indications!

I don't have the link anymore, but even MS said to ignore the 10016 errors.

gunrunnerjohn · Saturday at 1:44 PM

Ghot said:
I don't have the link anymore, but even MS said to ignore the 10016 errors.

One wonders why they generate them if they're giving that advice!

Ghot · Saturday at 1:51 PM

gunrunnerjohn said:
One wonders why they generate them if they're giving that advice!

It's not that... it's just that Event Viewer has gotten so out-of-hand that even MS doesn't care about it anymore.

Every now and then, it provides some useful info. But mostly... just ignore Event Viewer unless the computer isn't working properly.

glasskuter · Saturday at 2:39 PM

EV is a deep dark place. My rule of thumb is to NEVER go there unless I have a problem where it may point me in the general direction. EV is an area far above the full understanding of any lay person.

gunrunnerjohn · Saturday at 3:55 PM

There are some obvious errors that pop up there, and it's helped me track down a few things. In general, I have to agree with the "don't go there" advice. :lmao:

Timmy 2 toes · Saturday at 8:49 PM

Thanx everyone

Ghot · Saturday at 9:35 PM

glasskuter said:
EV is a deep dark place. My rule of thumb is to NEVER go there unless I have a problem where it may point me in the general direction. EV is an area far above the full understanding of any lay person.

It's not good for just anyone to "ponder" the ancient mysteries.

gunrunnerjohn · Saturday at 9:44 PM

Ghot said:
It's not good for just anyone to "ponder" the ancient mysteries.

Pondering is OK, but acting on them may bring disaster!

Scott · Sunday at 3:37 PM

@Timmy 2 toes give Snipping Tool a try. It's so much easier and faster than posting a photo.

Winuser · Sunday at 4:54 PM

I'm going to add my 2 cents to this thread. I highly recommend to to anyone and everyone that unless you're having problems to stay out of Event Viewer. I have to wonder why anyone would look for trouble when there is none.

Levitate11 · Sunday at 5:56 PM

Winuser said:
I'm going to add my 2 cents to this thread. I highly recommend to to anyone and everyone that unless you're having problems to stay out of Event Viewer. I have to wonder why anyone would look for trouble when there is none.

OCD. I like clean Event Logs.

glasskuter · Sunday at 6:17 PM

Levitate11 said:
OCD. I like clean Event Logs.

Good luck with that. I've never seen a 100% clean event log in my life, not even on a brand new virgin computer.

Winuser said:
I have to wonder why anyone would look for trouble when there is none.

You are so right. I've always thought MS shouldn't even make the event log so readily accessible to the user, especially for informational and recoverable events.

Quandary · Sunday at 7:55 PM

The Event Log was helpful when I had a networking issue between the Intel driver and the OEM router/modem. It allowed the conflict to be identified/isolated so that the appropriate pressure could be applied to the OEM to replace the device. Yes a rare situation.

SSD Question

Member

My Computer

Well-known member

My Computer

Member

My Computer

Active member

My Computer

aka Mama Glass

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

aka Mama Glass

My Computers

Well-known member

My Computers

Member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Active member

My Computer

aka Mama Glass

My Computers

Well-known member

My Computer

Similar threads