1

I had to re-enter Windows Admin credentials. When I ran the initial scan on the beta release it failed to scan inventory as there was no windows credentials. I re-entered in the settings.

3 Spice ups
2

So you’re saying the upgrade to 5.2 erased your admin credentials account in SpiceWorks?

-Jay

3

I have a similar issue, After the update several machines that used a specific login had to have credentials re-entered. The credentials were still in the spice works list however spiceworks seems to have lost the association. This was only 8 machines out of aprox 240 and it was the same account for all 8 of them.

4

24 out of 63 workstations and some servers all got the following message when rescanned Authentication failed because no Windows account was specified

When I try to reselect the Windows domain account to use and click Test Account I get wmi validation error: Description already exists

5

Only 1 of my Windows servers scanned sucessfully. All others failed as above.

All of my switches and VMWare host machines are OK.

6

Support should be here shortly to help.

-Jay

7

Hey guys,

I am going to attempt to recreate this issue for you. I’m assuming you are all using Non-production backups of 5.1? If so, can you give me your environment details? (where Spiceworks is installed, which OS, which version you upgraded from?) Thanks!

Cole

8

I copied a backup of 5.1 to a Windows 2008 R2 Ent VM. Version showing is 5.2.73044 of spiceworks.

I am using Internet Explorer 9, I installed version 5.1 copied the backup from the production and then ran the 5.2 beta installer to upgrade.

I installed Spiceworks in c:\program files (x86)\Spiceworks

There is no proxy in place for me and no running collectors, email settings are all Exchange.

9

Ben,

Can you elaborate on what you copied from 5.1? Was it the full data and db directories? or did you pick files?

Thanks,

Connie

10

Sorry, I was out yesterday.

  1. I intsalled Spiceworks 5.1 new install on a VM

  2. I deleted the db folder

  3. I backed up existing production Spiceworks, unzipped and copied out the db folder into the new installation.

  4. Then a ran the 5.2 Upgrade Beta installer.

I did however notice after I had backed up the production version that I had two zip files, one had a -1 on the end of the filename. Does this just mean that there was two backups for the same day?

11

I copied the entire folder and not just the files.

12

Hi Ben,

Thanks for the update. Those settings for the network scan are actually in the Data directory, not in the database so what happened when you only copied the Db directory was the network scan information wasn’t transferred over. When you move a Spiceworks install, you’ll need both directories as the database points to certain information in the Data folder. If you follow this how to , that should get you set up for testing out beta. Thanks!

13

Thanks, my bad! I did print this how to out when I did this but obviously I missed the part where it says data folder. Sorry guys. thanks. What I divvy.

Ben

14

Oh sorry guys still getting this problem again this morning after reinstalling and copying both data and db folders this time.

15

Hi Ben,

Sorry to hear that. When you look in C:\Program Files\Spiceworks\Data do you see a users.yaml file? If you open it, does it show your the user accounts you have set up for your scan ranges? Thanks!

16

Yes there is and yes it does.

Ta

Ben

17

If I click on the Manage Accounts button on a device that is getting the error and Create a New Windows account option and setup the windows account with a different description that fixes it. If I try to use an existing account that is when I get the wmi error.

It doesn’t work if I go to the Network Scan Settings and set a user account up in that, but does from the Manage Account dialog.

18

Hi Ben,

Thanks for the update. I just attempted to recreate the issue and was unable to. Here’s the steps I followed:

  1. Copied the Data and DB directories from my working 5.1 install into a new VM with 5.1 installed.

  2. Updated that install to 5.2

  3. Opened up the application and checked out the scan ranges and credentials - they appeared to be there and working correctly.

Do your accounts not show up in the beta at all under the Network Scans page, or do they just not work? Thanks!

19

If I go to Settings and Network Scans all the saved credentials are there from 5.1 backup. For some PC’s the scan works OK and all my procurve switches and VMWare hosts all working fine on scan.

When I select a PC which has the error and select Manage Accounts, if I select an existing account I get the error, if I enter new Windows credentials it works and automatically fixes all other PC’s with the same error.

There where some PC’s powered off yesterday and when scanned today have failed so again it won’t use existing credentials (even new ones as setup yesterday) I have to supply windows credentials again using a different description and it works.

I now have 4 Windows Admin credentaisl setup in Spiceworks which are all the same except the description.

20

Hi Ben,

Sorry for the delay. It sounds like you have found a bug. I am going to go ahead and create a ticket with our developers to take a look and I need one more piece of information from you to give to them. I am going to PM you with details on how to get that to me. Thanks!