Broblem with OWS and DMG 2

[lanpham_imported]

Dear all!
There is a problem, i am researching many today.
When I enter data ( first name, last name, extension...) in DMG. But data that is not display on OWS table when i type them out.( example: Extension. It shows red )
Please help me soon.
Thanks!

 

[parnum]

Check the RDS connection & run RDM.exe on the client and server, open OWS and check the local databse is populated (do the folders flash across the OWS screen on startup?)

Check the RDS plugs are green in OWS.

Possible permissions issue? are your client and server in the same domain? likely a windows problem.

best parnum

 

[lanpham_imported]

Sorry Parnum!
I didn't tell detail of this problem.
Old data still display on OWS table when i enter data in DMG before. But now i enter new data, that not display.
Best regard!

 

[parnum]

Yes, check what I said, OWS reads the ldb which updates via RDS

best parnum

 

[lanpham_imported]

Dear Parnum!
Many thanks for your help!
My new data displayed on OWS table very well.
The server has got many virus and full Hard Disk Drives.
Best regard!

 

[bojo3871]

Hi all,

We are experiencing the same thing for a customer.
What is it exactly we should look for when viewing RDM.exe for this issue?
The customer has D.N.A. 5.6 SP1 and SQL Server 2008. We checked the SQL table and we saw that the data changed (department name) in DMG did not reflect in the SQL table. OWS still sees the old data but DMG displays the updated department name.
The RDS and SQL plugs are green.

Hope anyone can help.

Regards,
Bojo

 

[parnum]

Open OWS on the DNAServer, does it reflect the change? if it does, your issue is permissions to the client(s), DNAServer updates the local database on a client, client reads the local db

best parnum

 

[bojo3871]

Hi Parnum,

Thanks for your reply. The OWS on the server does not reflect the changes. We have checked again today and the SQL now reflects the changes made in DMG, but OWS does not show the changes on the server and clients. Once I get the log from RDM, I will post snippets here.

Regards,
bojo

 

[bojo3871]

Hi parnum,

It seems to be SQL issue now but we do not know what caused it. Here is a snippet from RDM.exe:

[12/10/25 15:31:12] E1001 - Database Server Error(S1009): [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'security' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
[12/10/25 15:31:12] F4005 - Failed To Establish A Connection To Security Database Server
[12/10/25 15:31:12] F4006 - Failed To Allocate SQL Statement To Security Database Server
[12/10/25 15:31:12] E1110 - Local Database Population Event Failed - USRDB Table
[12/10/25 15:31:12] I7362 - Dumping Transaction Log Of SQL Security Database
[12/10/25 15:31:12] I7011 - Populating ATHDB Table
[12/10/25 15:31:12] E1001 - Database Server Error(S1009): [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'security' cannot be opened. It has been marked SUSPECT by recovery. See the SQL Server errorlog for more information.
[12/10/25 15:31:12] F4005 - Failed To Establish A Connection To Security Database Server
[12/10/25 15:31:12] F4006 - Failed To Allocate SQL Statement To Security Database Server
[12/10/25 15:31:12] E1111 - Local Database Population Event Failed - ATHDB Table
[12/10/25 15:31:12] I7362 - Dumping Transaction Log Of SQL Security Database
[12/10/25 15:31:12] I7012 - Populating PWDDB Table


And here is from SQL ERRORLOG:

2012-10-25 11:45:20.62 spid51 Starting up database 'dnadfdb'.
2012-10-25 11:45:21.90 spid51 Starting up database 'security'.
2012-10-25 11:45:23.49 spid51 WARNING: did not see LOP_CKPT_END.
2012-10-25 11:45:23.49 spid51 Error: 3414, Severity: 21, State: 2.
2012-10-25 11:45:23.49 spid51 An error occurred during recovery, preventing the database 'security' (database ID 7) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2012-10-25 11:45:24.00 spid51 Error: 3414, Severity: 21, State: 1.
2012-10-25 11:45:24.00 spid51 An error occurred during recovery, preventing the database 'security' (database ID 7) from restarting. Diagnose the recovery errors and fix them, or restore from a known good backup. If errors are not corrected or expected, contact Technical Support.
2012-10-25 11:45:26.54 spid52 Starting up database 'dirdb'.

 

[parnum]

OK, would exolain why the local db can't be updated if it can't access SQL via ODBC then. Over to the db restore, which of course has been backed up

best parnum

 

[bojo3871]

OK, would exolain why the local db can't be updated if it can't access SQL via ODBC then. Over to the db restore, which of course has been backed up

A slight problem there... used SQL 2008 Express and no backup. Can we do an SQL reinstall/repair then pump the exported DMG data back via DIRpop.exe? Or would a full re-installation of SQL and DNA be better? The other issue with that though would be re-requesting the license due to 4 OWS clients.

 

[parnum]

can you use export.exe to export the data from dirdb? if you can, export then reimport into a new sql install on the same server using dirdb

best parnum

 

[parnum]

you can install sql tools to administer express btw, check technet. no need to reinstall dna, just sort the sql.

best parnum

 

[bojo3871]

hi parnum,

if we cannot repair SQL, we will remove and re-install. after, we have to run the DNA installation (repair) to link DNA with the DB right? we have an export from dirdb that we can use.

 

[parnum]

If you are reinstalling SQL but not trashing the server, so DNA exists, then run the DNA install over the top again to recreate a blank database, then use DIRPOP to repopulate the database. If you are trashing the server, you will need to get it relicensed if ELM exists on the same server. SQL must be on the same Server at 5.6, ELM can be anywhere on the network.

If you have problems with running DNA over the top, uninstall and reinstall. Make sure DNA is at the same level as now when finished.

best parnum

 

[bojo3871]

Well, we reinstalled SQL and DNA. We were lucky the licenses were intact afterwards. The issue was resolved after this.

But there was some issue re-installing the clients. We had an access violation every time we ran the client installation from the shared folder from server even with the necessary credentials available. We got around it by running the installation from cd. Thanks.

 

[parnum]

You're welcome. With DNA it is often best to run the install locally.

best parnum