1 Reply by swtmike

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: Workstation Install Corrupted our Database?

Hello,

we're getting an 'EReadError: Stream read error'  and 'EStreamError: Out of memory whilst expanding memory system' when trying to connect to Recorder 6. This is a network installation on one server with three clients that's been running fine until earlier today when Recorder was installed on a new PC. After running Workstation.exe from the server as usual and allowing the installation to complete the main menu option 'Copy data from Recorder 2002 into this copy of Recorder 6' was selected then cancelled. Once cancelled the warning message below was displayed. I fear the worst in that our Recorder 6 database has been overwritten - is it possible to reassure otherwise?

Warning
Aborting the transfer of data at this point is very likely to leave the data and the programme unusable. You will need to either rerun the transfer from scratch or revert to a blank copy of the database in order to use the programme effectively. Are you sure you want to close the wizard now?

(Yes was selected)

2 Reply by johnvanbreda

  • johnvanbreda
  • Administrator
  • Offline
  • From: UK
  • Registered: 27-04-2006
  • Posts: 1,237

Re: Workstation Install Corrupted our Database?

The process which copies data from Recorder 2002 into Recorder 6 does refresh the database, and therefore could unfortunately have overwritten your database depending on what stage it got to. Do you have SQL Server Management Studio or any other tool that would allow you to connect to the NBNData database and check if the data is still present? Let us know if you don't or need help doing this.

You may find when you try to connect to the database that it simply does not exist as far as SQL Server is concerned. However, the underlying database files might still be present on the server disk. To check this, go to the server disk and look for the data folder associated with the SQL Server installation, for example mine is at C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data but this path will be different depending on how SQL Server was installed. In this folder, see if you have a file called NBNData.mdf. If so it might still contain your old data, or unfortunately it might be the new "fresh" database. If this is the case, again let us know so I can give you some guidance on reconnecting (attaching) this file to SQL Server.

If all that fails, do you have a  recent back-up of your data?

Best Wishes

John van Breda
Biodiverse IT

johnvanbreda's Website

3 Reply by swtmike

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: Workstation Install Corrupted our Database?

Hi John and many thanks for the reply.

We do have SQL Server Management Studio with which we get the error below when trying to connect to the Recorder instance.

Start of Error
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)

Additional information:
Database 'msdb' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information. (Microsoft SQL Server, Error: 926)
End of Error

There is an NBNData.mdf file on the server at 1.48GB which I'm hoping is our database and not a fresh one - what size is the fresh database? Should I just disconnect the current instance and just connect to the 1.48GB file?

Unfortunately our backup of this database has not been updated in a while.

4 Reply by johnvanbreda

  • johnvanbreda
  • Administrator
  • Offline
  • From: UK
  • Registered: 27-04-2006
  • Posts: 1,237

Re: Workstation Install Corrupted our Database?

The good news is that 1.48Gb sounds like your database is still there as it is too big to be the one straight from the installation. The bad news is that this seems a bit like SQL Server itself has got problems in a way that really Recorder should not be able to cause. Weird.

Anyway, the first thing I'd do is make a copy of that 1.48Gb file somewhere safe in case anything else goes wrong, and also make a note to setup regular backups in future! I think the correct way of recovering from this would be to restore a backup of the MSDB database, but assuming you haven't got one, uninstalling SQL Server, reinstalling it, then re-attaching the NBNData database would be an option. Do you have a reseller or suitable support to help you do this?

John van Breda
Biodiverse IT

johnvanbreda's Website

5 Reply by swtmike

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: Workstation Install Corrupted our Database?

The good news is that 1.48Gb sounds like your database is still there...

Phew! Hope at least. Yes, a big wakeup call re the backups. I'm happy to remove and reinstall SQL 2005 as long as that's not likely to interfere with a separate installation of SQL 2000 on the same server (we only installed 2005 on this server for Recorder a few months ago). Is it worth trying anything else beforehand?

Yes, it's a pity that clicking on the 'Copy data from Recorder 2002' option causes things to happen immediately as that option can be selected in error. But, as you say, if our backups were good we wouldn't have to worry.

6 Reply by swtmike (edited by swtmike 13-01-2010 10:40:21)

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: Workstation Install Corrupted our Database?

Hello again,

I've reinstalled SQL 2005, connected the NBNData_Data and can now connect to the database on the server ok but we're getting the 'EOleException: Login Failed for user' error when trying to connect from a PC. The error comes up when opening the application so I assume logon is automatic whereas before there was a Recorder logon screen. I did select Windows Authentication when reinstalling SQL so might this be the problem?

7 Reply by swtmike

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: Workstation Install Corrupted our Database?

Created a domain login after realising there wasn't one and changed authentication to SQL Server and Windows. Can now get to Recorder logon on the PC but get 'EReadError: stream read error' after entering logon details.

8 Reply by swtmike

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: Workstation Install Corrupted our Database?

We're still getting the errors in post one. SQL logs shows one error: 18456, Severity 14, State 11 relating to attempted logon. I believe state 11 means logon details are ok but server connection failed.

I'm unable to troubleshoot further without assistance - do we need a sql expert or a Recorder expert and is it possible to get a recommendation?

Thanks,
Michael

9 Reply by swtmike

  • swtmike
  • Member
  • Offline
  • Registered: 13-10-2009
  • Posts: 31

Re: Workstation Install Corrupted our Database?

Apologies for the delay in getting back. It turns out one of the tables was corrupted, possibly due to a log file issue which may in turn have been caused by a power outage over the xmas period.

Many thanks to MikeWeideli for getting us back on track.