626 Posts

February 13th, 2006 15:00

Is the host that you are viewing the details on a server that is running OMSA or a client/workstation that is running OMCI?

15 Posts

February 13th, 2006 16:00

I've actually tried it on both. There are also a couple features such as Alerts-->Logs and Tools-->User Preferences that are giving me
Error Code:1051
Error Message:Error in the SQL statement.
The database was originally on SQL server 2000 and I moved it to SQL server 2005. There seems to be some issues with SQL server 2005 and OM 4.5. I can connect back to the SQL server 2000 database and everything works fine. Any suggestions are welcome.

15 Posts

February 13th, 2006 18:00

UPDATE:

The device details are still missing even when connected to the sql 2000 database so it looks like that problem is related to upgrading from 4.4 to 4.5.

The other sql errors that I'm getting on 2005 I don't get on 2000. These errors all start when I try going to Alerts-->Logs. After I get the error there then I begin to have problems in the other areas.

626 Posts

February 13th, 2006 19:00

Are all of your discovery ranges still in IT Assistant?  Can you manually do an inventory and status update for all of your discovery ranges?  Wait enough time for it to complete and then see if anything has changed with respect to viewing the device details.  Let's try to solve that part of your problem first.  I think that the two things that you are seeing are separate issues.  I could be wrong though...  We'll see...

15 Posts

February 13th, 2006 20:00

Yeah I actually thought the exact same thing so I did an inventory and discovery scan. No dice.

1 Message

March 30th, 2006 16:00

I am getting the exact same error code:1051 when going to the logs section. It started as soon as I moved from using a local msde database to our SQL server which is running 2005. It looksl ike this must be related to 2005. Is there any known fixes for this?

15 Posts

March 30th, 2006 17:00

I ended up using SQL 2000. I contacted Dell and they didn't have any advice for getting it to work on SQL 2005. My guess is that it hasn't been tested on 2005 yet.

2 Posts

April 10th, 2006 14:00

I had this same issue, and it turns out there is a bug in the way SQL Server 2005 is handling the SQL statements from the Dell console. The following errors were logged in the SQLDump0001.txt file in the SQL Server logs folder :

Process 51 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

I installed SQL Server 2005 SP1 Community Technology Preview from

http://www.microsoft.com/downloads/details.aspx?familyid=39EBEF74-1C29-49FE-8221-C94F2B52F6C6&displaylang=en

and the errors disappeared. Apparently this bug will be fixed in SP1.

Hope that helps,
Gary Thorne
HAL Systems
No Events found!

Top