/build/static/layout/Breadcrumb_cap_w.png

K2000 Error1045 when deploying an Image

Hi all,

I've recently updated my K2000 to version 8.1 and after the update there was a warning that the Report User Database Password was the default one. I changed it and now every time I try to deploy and image I get an error 1045 that says "Access denied for user 'report'@'domain' (using passwords:YES) " whenever the mid-level task "Set ComputerName" runs (using the setcomputername.exe /k2mysql )

Any idea who to solve it?

Thanks in advance


0 Comments   [ + ] Show comments

Answers (2)

Posted by: KevinG 1 month ago
Red Belt
1
You could either edit the command line for the MID level task to include the new password or
    create a new one from scratch using the new wizard in 8.1.

Comments:
  • Thanks for your help, Much appreciated.
    Just to check, when editing the command I should add the /k2user:report /k2dbpass:password to it ,right? - Gwin 1 month ago
Posted by: Channeler 1 month ago
Red Belt
1

I would suggest you to modify your Task Command line (from Library), to something like this:

setcomputername_x64.exe /log /k1mysql /k1ipaddress:8.8.8.8 /k1dbname:KBDB /k1dbuser:report /k1dbpass:xxxxx

(Yes it says k1mysql, but just add your SDA IP, and your new password, at the end).

(This is for SetComputerName x64.exe)


Comments:
  • Thank you so much! Much appreciated.
    I works now but it seems to give the device a wrong name.
    I generally PXE boot the PC and once it appears in SDA under "Devices" I assign a hostname, reboot the PC and PXE boot it again and begin the deployment. but for some reasons the command is not picking up the hostname and generally assigning a new name to device. - Gwin 1 month ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ