Recent update causing revenge of the unknowns.

mark6589 · 2011-01-04T08:49:22.000Z

Around the time the last update was pushed out we have been all kinds of problems. We had a ton of devices we already had in inventory start to show up again. Also, tons of new WMI related errors out of the blue that were working just fine. Its kind of a mess so I disabled scanning until I can figure this out. Anyone have thoughts? I am confused as like I said, everything was just fine.

timjackson4638 · 2011-01-04T15:08:06.000Z

Which version of Spiceworks are you running right now?

Are you seeing devices showing up twice, new devices show up on used IPs or something different?

How is DNS on your network? Are there any stale records that need to be cleaned up?

mark6589 · 2011-01-04T15:55:59.000Z

I am seeing devices show up twice and not 100% sure why. I am running version 5.0.60041. As far as I know DNS is fine but ill check it.

timjackson4638 · 2011-01-05T07:00:24.000Z

If you haven’t looked through this How-To, try following at least #1 through #3 before your next full scan to see if that helps.

http://community.spiceworks.com/how_to/show/420

bytesnake · 2011-01-05T07:09:31.000Z

Follow TimJ42 !

Maybe you want to update to the new version ( Spiceworks Update 5.0.60932 Now Available ) too. In 5.0.60600 they already fixed a lot of issues.

mark6589 · 2011-01-05T07:59:37.000Z

@TimJ42 I have already gone thru that in the past. The options have been enabled already.

mark6589 · 2011-01-05T14:42:50.000Z

Now Im getting somewhere. The DNS suffex settings were just missing off the server spiceworks was on so I think DNS issues were causing the problem. However,. now thats its correct still getting WMI errors when trying to use windows ath. Inside spiceworks. I tried restart spiceworks but still no go. Only thing else I can try is restarting the whole system this eveing.

bytesnake · 2011-01-06T00:24:39.000Z

You could follow this without #2: Speeding up spiceworks (still not sure if this will help).

timjackson4638 · 2011-01-06T06:44:53.000Z

Have you tried testing WMI outside of Spiceworks (i.e., run the wmic test)? Does that work as expected or return an error?

mark6589 · 2011-01-06T08:18:15.000Z

It a appears a bunch of computers (a dozen or so) are totally failing WMI. Getting the dreaded 0x80070005 error access is denied. All these computers use to work fine. What could have caused this?

timjackson4638 · 2011-01-06T09:50:07.000Z

So if I’ve understood correctly, you are now seeing an access denied error testing WMI outside of Spiceworks?

Assuming these are domain machines, there could be a change in the firewall settings or A/V blocking firewall access (any recent GPO changes?). Does the account tested have local admin rights on the machine? WMI and DCOM services are up and running?

mark6589 · 2011-01-06T09:55:37.000Z

As far as I know there have not been any changes in the GPO’s at all. Standard GPO has windows firewall disabled.

mark6589 · 2011-01-06T12:22:41.000Z

I also tried the WMI fix script that was posted on spiceworks that I had saved. I HATE the0x80070005 error… Since the script didnt work I have no idea what else to try.

timjackson4638 · 2011-01-06T14:15:31.000Z

Yes, that can be tricky error to diagnose. Is there anything similar with the machines that are failing? Has anything else changed or been updated on them recently? Which OS(es)?

It might be easier to pick one and just start with that.

mark6589 · 2011-01-06T14:48:39.000Z

Honestly pretty much SOL. I have never been able to fix a 0x80070005 error if the script couldnt fix it.

mark6589 · 2011-01-20T09:23:55.000Z

This turned out to be related to my spiceworks database being corrupt. Thanks for all your help

timjackson4638 · 2011-01-20T09:55:45.000Z

Thanks for posting that back. Hope you get it all celaned up!