StefanPahrmann

Do'h - you're right about the last one with the 's' - bad sight must come with age . The space was just an error while copying from putty. Thanks, it's working as a charm now. Regards Stefan

Hi again, just tried that, same error (see output, I have a screenshot as well). Passwords in lists can be created and passwords can be generated. Any logfiles to look into or some hints on how to debug? curl -k --request POST https://webserver:9119/api/passwordswordlists -d "PasswordList=ZZZ3-Test" -d "CopyPermissions FromTemplateID=1" -d "CopySettingsFromTemplateID=1" -d "APIKey=xxxxxxxx" [{"errors":[{"message":"Invalid API Call"},{"phrase":"Error = Object reference not set to an instance of an object.}]}] curl -k --request POST https://webserver:9119/api/passwordswordlists -d "PasswordList=ZZZ3-Test" -d "CopyPermissions FromTemplateID=1" -d "CopySettingsFromTemplateID=1" -d "APIKey=xxxxxxxx" [{"errors":[{"message":"Invalid API Call"},{"phrase":"Error = Object reference not set to an instance of an object.}]}] Both PasswordListID and TemplateID do exists. -Stefan

Hi again, I tried that as well. Can you tell me which fields are mandatory, so that I can do a passwordlist-creation with as few options as possible (a shared passwordlist)? I think the documentation is a bit unclear on that topic :-) Regards Stefan

Hi, When trying to create a passwordlist I get an error (this is just a minimalistic query): [{"errors":[{"message":"Invalid API Call"},{"phrase":"Error = Object reference not set to an instance of an object.}]}] The error I get is following: [{"errors":[{"message":"Invalid API Call"},{"phrase":"Error = Object reference not set to an instance of an object.}]}] I tried several options, taken from your documentation, but can't see what I'm missing. Creation of passwords with the same URL (only "password" instead of "passwordlist") works as expected. I'm using build 7476. Regards Stefan Pahrmann

Hi again, I tried the upgrade again, and checked the query (with 0 rows affected) before. I rebooted the server to rule out some "hanging" process. It failed with exactly the same error again. Do you want me to open a supportcase or can we continue here in the forum? -Stefan

The problem with a restore is, that the service was "open" for end users after the failed upgrade and that some passwords probably were updated/newly created. Is there a way to tell which passwords are updated/created after e.g. 2 PM yesterday and by whom (eventually by SQL query)? I could either try to contact them or migrate them by myself afterwards manually? -Stefan

Hi, It's a bit tricky to do a restore, since i needed to rollback and a simple replacement of the files did seem to work. I would rather doing that. Is there some other way? Can we do it with the backup from before the upgrade? It's true I tried to run the upgrade several times, here is the first output: 13-01-2015 13:05:06 - Build 7000 - Step 2 Completed Successfully. 13-01-2015 13:05:44 - Build Process 'Build_7000_DataUpdates' failed with the following error - Query+timeout+expired ::: +++at+System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior+behavior%2c+String+method)%0d%0a+++at+System.Data.OleDb.OleDbCommand.ExecuteNonQuery()%0d%0a+++at+Passwordstate.Upgrade.Build_Schema_Data_Updates(String+sqlScript%2c+String+LogFileDetail) 13-01-2015 13:05:44 - Build Process 'Build_7000_Updates' failed with the following error - Thread+was+being+aborted. ::: +++at+System.Threading.Thread.AbortInternal()%0d%0a+++at+System.Threading.Thread.Abort(Object+stateInfo)%0d%0a+++at+System.Web.HttpResponse.AbortCurrentThread()%0d%0a+++at+Passwordstate.Upgrade.Build_Schema_Data_Updates(String+sqlScript%2c+String+LogFileDetail)%0d%0a+++at+Passwordstate.Upgrade.Build_7000_Updates() Regards Stefan

Hi, I'm trying to upgrade from 6.350 to 7.105, but I'm getting an error during step 2: "Thread was being aborted" at Passwordstate.Upgrade.Build_Schema_Data_Updates. Looking into the logfiles I've found this: 13-01-2015 13:19:00 - Build 7000 Upgrade Started. 13-01-2015 13:19:00 - Build Process 'Build_7000_SchemeUpdates_Part1' failed with the following error - Column+names+in+each+table+must+be+unique.+Column+name+%27FQDN%27+in+table+%27dbo.ADDomains%27+is+specified+more+than+once. ::: +++at+System.Data.OleDb.OleDbCommand.ExecuteReaderInternal(CommandBehavior+behavior%2c+String+method)%0d%0a+++at+System.Data.OleDb.OleDbCommand.ExecuteNonQuery()%0d%0a+++at+Passwordstate.Upgrade.Build_Schema_Data_Updates(String+sqlScript%2c+String+LogFileDetail) 13-01-2015 13:19:00 - Build Process 'Build_7000_Updates' failed with the following error - Thread+was+being+aborted. ::: +++at+System.Threading.Thread.AbortInternal()%0d%0a+++at+System.Threading.Thread.Abort(Object+stateInfo)%0d%0a+++at+System.Web.HttpResponse.AbortCurrentThread()%0d%0a+++at+Passwordstate.Upgrade.Build_Schema_Data_Updates(String+sqlScript%2c+String+LogFileDetail)%0d%0a+++at+Passwordstate.Upgrade.Build_7000_Updates() Doing a query select * from dbo.ADDomains gives following: 1 xxxx dc=corp,dc=xxxx,dc=com 1 NULL NULL NULL With FQDN as the 5th column (NULL) Can you give some hints, what to do? Regards Stefan

Hi, When creating a new username/password with the API with an expirydate, these passwords will not be rotated, even if the password list has set this as default behavior for each new password. When selecting the password, rotating is not enabled (hence not inherited). Creating a new user/password manually through the GUI works as expected though. Am I missing something? Regards Stefan

I really hoped you had changed the way to authenticate in this new major release. Is it something you still consider? Regards Stefan

It's the same this way around. I've sent a mail with the requested information. Regards Stefan

Hi, When trying to Edit password list details (regardless of which passwordlist), I get an error (see attachment, it's pretty generic) Any hint? Regards Stefan

Hi again, I've finally could test with the user again, and it looks like we're not able to reproduce the error. Would you still have the mail with the data? Regards Stefan

No problem, I was busy too We have a password policy which is named like "<company> Standard". This is linked to a template. When looking into the Password policies I still can see the above. Regards Stefan

Just an update - I misunderstood the users. It's after a search (where they just want to confirm that a user doesn't exist), when they click "add" that the error occurs. -Stefan