We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

PC Scale Tower - SQL Server Rebuild

Medium Priority
337 Views
Last Modified: 2012-05-07
I lost my SQL server a couple of weeks ago to a lightning storm.  I realized after the fact that my backups were backing up files, but no SQL Server agent to save all my SQL database/connection info.  This SQL server has only one purpose... to house the databases for an application we pull historical data from called PC Scale - Tower.  It seemed like a simple phone call to the "Tower" people to help set it back up.  Well, they are refusing to help us.

So, I have no idea how any of this was setup before and I'm having no luck making it work.  Does anyone out there use PC Scale Tower that might be able to lead me through some specific setup issues, or even provide some documentation on the SQL Server setup?  We're willing to pay for phone/remote support, but I can't find anyone to take our money.

Your help is greatly appreciated.
Comment
Watch Question

Most Valuable Expert 2014

Commented:
Can you access the disk(s) at all?

Can you access the C:\Program Files\Microsoft SQL Server\MSSQL.#\MSSQL hive?

Or  do you have backups of the master and model databases as well as your data databases?

If so -- there are a number of ways to recreate your SQL databases and get close to your original setup.

Author

Commented:
I have the databases.  I've reinstalled SQL Server 2005 to my newly built server and attached the old databases.  It appears that my users are orphaned, so I can remove the DB_Owner user, "tower", then recreate that user but I don't know the password to assign it.  So, my application fails with a "An error occurred in the Retrieve Client Files Service: Login failed for user 'tower'." message.  It appears that the application is hard coded to access the database via user 'tower' with a password that I do not know.

Is there an easy way to recover the password from an orphaned user?
Most Valuable Expert 2014

Commented:
You didn't recover the original Master DB I take it?

Do you have a copy or backup of the original master?

If you can restore it -- then it should be as before the crash.  

Or alternatively -- I have not tried this, so I won't guarantee it will work. If you can restore the master DB as something like master_temp. Then copy the sp_help_revlogin from the link below. Where it says master change it to master_temp. Then run the procedure to extract the logins.

How to transfer logins and passwords between instances of SQL Server
http://support.microsoft.com/default.aspx?kbid=246133

Author

Commented:
I'm sorry, let me explain better/differently... My server's C: drive died, but all of my SQL databases were on the D: drive in a safe place.  I fired up a new C: drive and installed Win2k3 Server, then Backup Exec, then restored my backups from the previous day.  Backup exec 9.1 was set to backup everything on the C: drive, but did not have any SQL Agents or "system state" options.  So, I restore the entire C: drive and see that my SQL Server did not fix itself after the file recovery.  I then installed SQL 2005 and reattached the databases from my D: drive.  That directory on my D: drive still has the "master" and the "model" databases in it along with all the others, but it appears that my most important user, "tower", cannot connect to the database "COMPANYDATA" because ???  I was told by someone better with SQL than I that the users were orphaned.  Does this make any sense?

I'm wodering too... if I installed Win2k3, then SQL 2005, then backup exec and did the recovery if I would get a different result.  
Most Valuable Expert 2014
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview
Most Valuable Expert 2014

Commented:
If the user doesn't respond -- I would say delete -- no refund.

It would have been nice to see if my suggestions would have worked, but to have this lying around in an "un-proven" state -- not a good thing.

Author

Commented:
Jimpen-
You provided some very good information and links to some good resources.  I was not able to get my SQL server back to a running state with this information, but helped me determine that I do not have all appropriate pieces to put this puzzle back together.  Thank you.
Most Valuable Expert 2014

Commented:
I'm sorry that you couldn't get it back to its original state. Thanks for letting us know.

May all your days get brighter and brighter.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.