Archive

Archive for the ‘Computers’ Category

Quick Post: Windows Update Error 80073712

March 17, 2017 Leave a comment

When installing a Windows Update, you receive an Error Code 80073712.

According to https://support.microsoft.com/en-us/kb/947821, 80073712 is ERROR_SXS_COMPONENT_STORE_CORRUPT The component store is in an inconsistent state.

From KB947821 I downloaded & ran the tool for my version of Windows. It can take a while.

When it was finished, I checked C:\Windows\Logs\CBS\CheckSUR.log. It found one error.

Doing a Bing search for part of the bad manifest, I was able to determine it was KB3150513. I manually downloaded the update from the Microsoft Update Catalog (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB3150513) then installed it on the computer. No more error!

Side note:

I didn’t have to do this but may have to also reset the Windows Update Components (https://support.microsoft.com/en-us/kb/971058)

Backlog: ODBC Connection Failed

March 17, 2017 Leave a comment

So you’ve got a Microsoft Access database with linked tables to a SQL server that looks something like this.

When opening one of the linked table you get an error that says, “ODBC–connection to ‘DP’ failed”.

When you click OK you get a message that says, “Microsoft Access can’t open the table in Datasheet view”.

Hmm, what up with the ODBC connection called “DP”? What say you Procmon?

Result = NAME NOT FOUND. Oh, the ODBC connection doesn’t exist. Create the ODBC connection & you are good to go.

I admit that you could have also just gone & looked at the ODBC connections in the Control Panel to figure out it doesn’t exist but it was really just an excuse to use Procmon.

Backlog: ZIP instead of XLSX

March 17, 2017 Leave a comment

As an ode to Stephen Colbert this is Part 1 of my open-ended series…“Backlog”. ZIP instead of XLSX! These will admittedly be old topics but I’m clearing out a “backlog” of draft blog posts.

I got a report from a user that was trying to download an Excel file from our company’s Intranet that it was prompting him to save it instead of just opening it as it always has. Taking a look at it I see that it is prompting to open it however the file type is being identified as a zip file.

If I click Open I get the prompt the user was talking about where Save or Cancel are the only options.

Luckily since this is an internal web server it can be fixed. The issue is that the web server does not know how to handle the XLSX file type (i.e. MIME type). To fix this use the following steps to add the MIME type for the XLSX MIME type as well as a few others listed at the end.

  • Open IIS Manager.
  • Right click Servername & select Properties.
  • Click the MIME Types button.
  • Click New.
  • In the Extension field type xlsx
  • In the MIME type field type

application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

Categories: Computers Tags: , , ,

Disable Automatic Updates for Power Query for Excel

October 28, 2016 Leave a comment

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Power Query for Excel]
“DisableUpdateNotification”=dword:00000001

or

New-ItemProperty -Path “HKLM:\SOFTWARE\Wow6432Node\Microsoft\Microsoft Power Query for Excel” -Name “DisableUpdateNotification” -PropertyType DWORD -Value 1

“Error loading this resource” when playing a video on Lynda.com

August 12, 2016 Leave a comment

I had a user reporting that when trying to view a video on Lynda.com they kept getting an error that said, “Error loading this resource”.

Error

They would only get this error when logged onto a Remote Desktop Server. It worked just fine on their PC.

Turns out there is an update for the “Desktop Experience” feature for Windows Server 2008 R2 that adds support for the H.264 video & AAC audio formats. After the update was installed it played great.

The update is KB2483177.

Quick Post: 0x00000002 Error Adding a Printer

When adding a printer you receive an error that says, “Windows cannot connect to the printer. Operation failed with error 0x00000002”

0x00000002

Unfortunately the only thing I have ever found to resolve this is restarting the print spooler service.

Categories: Computers Tags: , ,

Error Changing Drive Letter

When changing the drive letter in Disk Manager you may receive an error that says, “The parameter is incorrect”.

DM_ParameterIncorrect

This can happen is the pagefile is on that drive. Move the pagefile to a different drive, reboot, then try again.

Users not receiving email about an expiring password

February 16, 2016 2 comments

WARNING – This post deals with making bulk changes to Active Directory. Proceed at your own risk.

I’ve been using the script (with a few tweaks) from http://rlmueller.net/PasswordExpires.htm to send users an email notification when they are within the configured Prompt user to change password before expiration policy. It works great but every once in a while a user would call because their password had expired & they did not receive the email. Over time occasionally that same user or a few other ones would call with the same issue.

Finally, one day another user called describing the same thing. Time to get to bottom of this one. I took a look at the user’s Active Directory account & sure enough the pwdLastSet attribute was over 90 days old. I took my script & modified it so I could just see the results without sending any emails. Your results with the original script may vary but at a minimum comment out the line that sends the email & instead pipe the output to the console.

# SendEmail $Mail $Notice

Write-Host $Name”,”$PwdExpiresDays

Sure enough when I ran it the user reporting the issue was not showing up in the results.

The script filters the results a little as noted below.

$Searcher.Filter = “(&(objectCategory=person)(objectClass=user)” `

   + “(pwdLastSet>=” + $($64Bit1) + “)” `

   + “(pwdLastSet<=” + $($64Bit2) + “)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=2)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=65536)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=32)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=48))”

So I modified the filter (see below) to just show all users & ran it again. This time the user having the issue showed up.

$Searcher.Filter = “(&(objectCategory=person)(objectClass=user))”

So at least now I know the script is working but for some reason the user is being filtered out. I add each filter back one at a time to figure out which one is causing the user to be excluded. I skip over the two pwdLastSet filters because the account is already at 0 so that could cause it to not show up. So now my filter looks like this:

$Searcher.Filter = “(&(objectCategory=person)(objectClass=user)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=2))”

 

The user still shows up. On to the next one.

$Searcher.Filter = “(&(objectCategory=person)(objectClass=user)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=2)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=65536))”

 

Still there…next.

$Searcher.Filter = “(&(objectCategory=person)(objectClass=user)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=2)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=65536)” `

   + “(!userAccountControl:1.2.840.113556.1.4.803:=32))”

 

Bingo! The user isn’t showing up. So I do a little checking & find that !userAccountControl:1.2.840.113556.1.4.803:=32 will exclude users that aren’t required to have a password. Huh? Now why would any of my user accounts be configured to NOT require a password? So that begs the question, how many users are configured like this? I run the following Powershell command. The results will vary depending on your environment but suffice to say you do not want a lot. (Hint hint some may legitimately need to be configured like this.)

Get-ADuser -LDAPFilter “(userAccountControl:1.2.840.113556.1.4.803:=32)” | Select-Object name

You can even see this by looking at the userAccountControl attribute in AD & see that it is set to PASSWD_NOTREQD | NORMAL_ACCOUNT.

In all my years I’ve never seen this before so I did a little digging & ran across this TechNet post.

http://blogs.technet.com/b/pfesweplat/archive/2012/12/11/do-you-allow-blank-passwords-in-your-environment.aspx

Long story short, a long time ago when “someone” migrated user accounts they may have done it wrong.

But enough pointing fingers, how to fix it. Use the Set-ADUser command to set the user’s PasswordNotRequired flag to $false.

Set-ADUser -Identity jsmith -PasswordNotRequired $false

I’ll leave it up to you how you want to modify all the affected users. Just be careful as there may be a legitimate account that needs this setting. Again, proceed at your own risk. I just filtered based on OU.

Get-ADuser -LDAPFilter “(userAccountControl:1.2.840.113556.1.4.803:=32)” -SearchScope Subtree -SearchBase “OU=Company,DC=contoso,DC=com” | Set-ADUser -PasswordNotRequired $false

Quick Post: Windows Update Error 13EC

February 11, 2016 Leave a comment

I know another Windows Update post. I’m just going through a backlog of stuff that I never published & just want to get it up here.

A while back I wrote about a very similar error when installing the .NET 4.0 Framework (KB982671). https://patrickhoban.wordpress.com/2010/09/29

When installing the .NET 4.5.2 Framework (KB2901907) you receive an error code 13EC.

1 13EC

If you try to install it manually you get an error that says, “An error was encountered. Unspecified error.”

2 13EC

If you watch the free space while installing the update you will see it drop down next to nothing.

3 13EC

I tried to free up some space by doing normal disk clean up (i.e. delete temp files, old profiles, etc.), shrank the WinSXS folder (dism /online /cleanup-image /spsuperseded). It got a little further but still no dice. Luckily it was a VDI so I could just “give” it more hard drive space.

4 13EC

I ran the update again & this time it worked.

5 13EC

As referenced in https://www.microsoft.com/en-us/download/details.aspx?id=42642, this update requires 4.5GB of free space for both x86 & x64.

Quick Post: Windows Update Error 8007045D

February 3, 2016 Leave a comment

When installing Windows Updates it fails with an error code 8007045D.

8007045D

You also see an error in the System log with an Event ID 57 & Source of NTFS that says, “The system failed to flush data to the transaction log. Corruption may occur.”

8007045D-2

To resolve the issue run a check disk. Be sure to select Automatically fix file system errors & Scan for and attempt recovery of bad sectors then click Start.

8007045D-3

Click Schedule disk check & reboot the computer.

8007045D-4

Categories: Computers Tags: , ,
%d bloggers like this: