- This topic is empty.
10. September 2007 at 22:05 #595
I’m having trouble installing WDM on a new server. I have a fresh install of SQL 2005 Express on a Windows server 2003 R2 with SP2, trying to install WDM 4.5.1.
Hereâ€™s a little background on the server and what I have tried. The server was originally named serverbuild as it was being installed; it was then renamed when it went into production.
I did a
to get the correct name in sql.
I then proceeded to install WDM, and it gave an error saying “Unable to attach the Wyse Device Manager database”. I thought it may be related to my sa password, which contained an @ symbol. I thought that may not be acceptable because of complex security and 4.5.1. I changed the password to contain only letters and numbers but the install still failed with the same error.
I’m not sure where to go from here. Can anyone give some suggestions? Thank you for your responses.11. September 2007 at 13:02 #10175
open the SQL Manager to edit the WDM database. Look in the INSTALL table and check the entries there. There should be some entries with servernames, etc. If the naming isn’t correct, fix it manually.
ConfGen11. September 2007 at 13:53 #10178
ConfGen, thanks for the quick response.
The DB never gets created, which is why I thought it was an issue with the sa password. When I open SQL Manager it is just the stock install no DB’s at all.
I also thought it may have to do with the compatibility level in sql 2005. The default is SQL Server 2005 (90). Is there a way to set a global compatibility level of SQL Server 2000 (80)?11. September 2007 at 14:18 #10180
Does “Production” mean that the server is part of your domain? Then there is for sure an issue to complex passwords.
Do you have a chance to disable the use of complex password in your domain for a few minutes and install WDM in the meantime?
ConfGen11. September 2007 at 15:00 #10182
Yes, it is on the domain. Could you explain how to disable complex passwords? I believe that would be possible for this machine for a short time.
Thanks again for the quick response.11. September 2007 at 15:18 #10183
This has to be done in the GPO for the domain controller
ConfGen11. September 2007 at 15:39 #10184
Would 4.5.1 SR1 be a solution for the complex password issue?11. September 2007 at 18:42 #10187
Yes, the SR1 release is fixing this issue.12. September 2007 at 14:44 #10190
I downloaded and tried to install 4.5.1 SR1 and received the exact same message as before.
Complex passwords are still turned on in the domain, however the sa password does not contain any complex characters.
I guess my next step is to have the network admin disable complex passwords for about 10 mins to get this installed. Once WDM is installed and while complex passwords are turned off what changes will I need to make to the DB so that when complex passwords are turned back on WDM still functions?12. September 2007 at 15:17 #10191
SR1 is using a complex password for the local DB user rapport. So no changes are needed.13. September 2007 at 2:14 #10195thinkthinMember
- Total Post: 1707
- Jacked into The Matrix
I was sent these instructions on using SQL express with WDM, I have not tried them however it may be worth a shot. Also I will post the steps to “manually” install the WDM DB on SQL 2005 with complex passwords.
– An issue was encountered with the default installation of SQL 2005 Express which prevented WSM from properly connecting to its database.
– The standard SQL 2005 Express installation gives you an option for â€˜Instance Nameâ€™ and by default uses an instance name of â€˜SQLExpressâ€™. If this is not changed to â€˜Default Instanceâ€™, it prevents WSM from properly working.
– Steps to install SQL 2005 Express:
1/ Run standard SQL 2005 Express installation but make 2 changes during installation:
2/ Uncheck â€˜Hide Advanced Configuration Optionsâ€™
3/ Select â€˜Default Instanceâ€™ and NOT â€˜Named Instanceâ€™ SQLExpress (note, it defaults to â€˜Named Instanceâ€™)13. September 2007 at 7:32 #10196
Good hint, but only saw that on WSM not WDM
ConfGen13. September 2007 at 10:31 #10197thinkthinMember
14. September 2007 at 8:40 #10208
- Total Post: 1707
- Jacked into The Matrix
I think I know the issue now.
Remove SQL Express and reinstall it afterwards. But install it in Mixed Mode Authentication. I am pretty sure you have just use Windows Authentication now.
When installing WDM afterwards use the SA account when prompted for the SQL credentials with the password of your SA you’ve entered during the SQL Express install.
ConfGen18. September 2007 at 15:26 #10233
Thanks for all the responses guys, we have decided to wait until 4.5.2 is released.
ConfGen, mixed mode authentication was installed from the begining, that was a good sugesstion though. I will keep you up to date on the progress of the install once 4.5.2 is released.
Thank you all for your support and suggestions.
- You must be logged in to reply to this topic.