SQL08x_08 Appliances

[BeckyHester]

This topic is dedicated to questions and comments related to the SQL08X_08, SQL08WG_08, SQL08D_08, SQL08W_08, SQL08S_08, SQL08E_08: Microsoft SQL Server Database Appliances.

These appliance will be included in the AppLogic 2.9 GA release.

The SQL08 data sheet can be found at http://doc.3tera.net/AppLogic29/CatDatabaseAppliancesSQL.html. (page will be published concurrently with 2.9 GA release)

Please post any questions and/or comments here.

[tanpa09]

I'm trying to use the SQL08S_08 appliance and it keeps failing to start.
May 9 11:34:41 xx-xxxx-xxxxxx applogic: [803:error s:47]: srv5: Windows_Build_Pat:main.SQL08S_08: 'sa' password wasn't set in 3 tries
May 9 11:34:41 xx-xxxx-xxxxxx applogic: [803:error s:47]: srv5: Windows_Build_Pat:main.SQL08S_08: appliance start failed
May 9 11:34:41 xx-xxxx-xxxxxx applogic: [233:error s:47]: srv5: VM 'vm.srv5.Windows_Build_Pat.main.SQL08S_08' failed to start

I’ve set the password in the properties of the appliance and I’ve left the password field blank, neither works. I’ve tried passwords of 8 or more characters, and less than 8 characters. I’ve changed the name of the application so that it is less than 15 characters long (mentioned in the documentation page for the appliance). I started the appliance in debug mode and tried to login, but I don’t have the admin password. I tried to change the admin password with wincfg but it couldn’t get access, said to check if the firewall was blocking port 22.

How can I get this appliance to work?

[tanpa09]

I figured it out, nevermind.

[PeterNic]

tanpa09, please let us know what the problem was / how to fix it if someone sees it again or whether we can improve the error message.

Thanks,
- Peter

[tanpa09]

I made 3 changes to get the SQL appliance working: I changed the application name (documentation mentions keeping it below 15 characters); made sure the password length was more than 8 alphanumeric characters, and cleared out all other values on the properties sheet. I suspect it was either the application name or the other values on the properties sheet causing the errors.

[PeterNic]

From Andy B.:


Hi Peter, I was reading this post the other day because I had the same error about setting sa password. I went through all of the solutions without success. Finally I started the application in --debug mode and logged in and looked at the event log...the MSSQLSERVER service was not started. I looked at the service props and saw that the sqlservr.exe reference pointed to a non-existent directory. Sure enough, drive D: did not contain the SQL Server install.

The problem? To "save time" I had tied the D: drive to a data volume with 500MB. In my defense, some error message like "volume space exceeded" would have told me my error at once; however, I resized the volume to be a more respectable (but still small-ish) 6GB and restarted the app. Problem went away!

It turned out not to be the length of the application name (mine was longer than 15 chars initially but I had changed it) nor on the strength of the sa password. It was plain and simple not enough space. Hopefully this helps someone else -- I cannot post to that forum (put in request for it 48 hours ago!) so I hope you can add it.

v/r,
Andy B


Thanks Andy!