Latest Updates

DBSPI40-1: Unable to fetch data from table 'sysfiles' [System.NullReferenceException: Object reference not set to an instance of an object. at ovam_ito_send_multi(ovam_mdata* , Double , SByte* , SByte* ) at metric3215_90(ovam_mdata* data, Double* mw_value)].


Kindly suggest solution for this error on windows platform.

Thanks in advance.

Hi hemmanth,

try executing dbspicam -m 278 -v -p in your machine... and see if there is any error message like,, cannot create temp folder...

if that is the case, do
dbspicol OFF

Then clear all the files under,
c;/usr/ov/dbspi/temp

restart the collection

dbspicol ON
--------------------

else

chek for any hung preocesses (check if there are two processes for collecting the same data.)

if yes, then kill one of the process.

let me know how it goes!!

Hi,

Please see output for dbspicam -m 278 -v -p

C:\Documents and Settings\hparalkar>dbspicam -m 278 -v -p
"Could not get version from osql.exe."
"Report cannot be generated."

Server: 'dkafr-ms051\SQLEXPRESS' @ 'c:\Program Files\Microsoft SQL Server\MSSQL.
1\MSSQL'
-------------------------------------------------------------
dkafr-ms051\SQLEXPRESS: 3278 0,01 objext=master:LOG_GROUP database_name=master f
ilegroup_name=LOG_GROUP
dkafr-ms051\SQLEXPRESS: 3278 0,02 objext=master:PRIMARY database_name=master fil
egroup_name=PRIMARY
dkafr-ms051\SQLEXPRESS: 3278 0,00 objext=tempdb:LOG_GROUP database_name=tempdb f
ilegroup_name=LOG_GROUP
dkafr-ms051\SQLEXPRESS: 3278 0,01 objext=tempdb:PRIMARY database_name=tempdb fil
egroup_name=PRIMARY
dkafr-ms051\SQLEXPRESS: 3278 0,00 objext=model:LOG_GROUP database_name=model fil
egroup_name=LOG_GROUP
dkafr-ms051\SQLEXPRESS: 3278 0,01 objext=model:PRIMARY database_name=model fileg
roup_name=PRIMARY
dkafr-ms051\SQLEXPRESS: 3278 0,01 objext=msdb:LOG_GROUP database_name=msdb fileg
roup_name=LOG_GROUP
dkafr-ms051\SQLEXPRESS: 3278 0,05 objext=msdb:PRIMARY database_name=msdb filegro
up_name=PRIMARY
dkafr-ms051\SQLEXPRESS: 3278 0,02 objext=SharePoint_Config:LOG_GROUP database_na
me=SharePoint_Config filegroup_name=LOG_GROUP
dkafr-ms051\SQLEXPRESS: 3278 0,07 objext=SharePoint_Config:PRIMARY database_name
=SharePoint_Config filegroup_name=PRIMARY
dkafr-ms051\SQLEXPRESS: 3278 0,01 objext=SharePoint_AdminContent_de1e0b99-9158-4
327-b23b-dfa64dc02488:LOG_GROUP database_name=SharePoint_AdminContent_de1e0b99-9
158-4327-b23b-dfa64dc02488 filegroup_name=LOG_GROUP
dkafr-ms051\SQLEXPRESS: 3278 0,44 objext=SharePoint_AdminContent_de1e0b99-9158-4
327-b23b-dfa64dc02488:PRIMARY database_name=SharePoint_AdminContent_de1e0b99-915
8-4327-b23b-dfa64dc02488 filegroup_name=PRIMARY
dkafr-ms051\SQLEXPRESS: 3278 0,11 objext=WSS_Content:LOG_GROUP database_name=WSS
_Content filegroup_name=LOG_GROUP
dkafr-ms051\SQLEXPRESS: 3278 2,33 objext=WSS_Content:PRIMARY database_name=WSS_C
ontent filegroup_name=PRIMARY

Hi ,

This is a dbspi settings problem.

the DB admins should be able to fix this issue..

if you can hold for 2 days,, i will provide a fix for this.....

bye for now!!

Hi,

Could I have any update on the above issue...

Thanks in advance for your reply.

First we must use OSQL to see if it is DBSPI fault or DBA configuration or MS SQL authentication problem.


Let’s assume we have this problem:



OVOserver# opcdeploy -cmd 'dbspicam -dvfp' -node tforsell.pa.com

Checking server: 'TFORSELL'

Connect: OKAY



"Could not get version from sqlcmd.exe."

"Report cannot be generated."



Check first how DBSPI has been configured to see if there is/are passwords defined for MS-SQL instances or not:

OVOserver# opcdeploy -cmd ‘dbspicfg -e’ -node tforsell.hp.com

SYNTAX_VERSION 4

MSSQL

SERVER "TFORSELL " CONNECT "sa/dbspi_pw"

SERVER "TFORSELL\Inst1" CONNECT "sa/dbspi_pw"


So above there is a user/password defined, thus we will use this command with –U and –P parameters

OVOserver# opcdeploy –cmd ‘osql -U sa -P dbspi_pw -S TFORSELL\Inst1 -Q "select @@version"’ –node tforsell.pa.com


If there would be no user/passwords, like below (see the Inst1 line):



OVOserver# opcdeploy -cmd ‘dbspicfg -e’ -node tforsell.pa.com

SYNTAX_VERSION 4



MSSQL

SERVER "TFORSELL " CONNECT "sa/dbspi_pw"

SERVER "TFORSELL\Inst1"

Then the command would have been like below, to use Integrated authentication without password, i.e. it will just connect to the database and the SQL database decides if it will allow the OVO agent username to connect (usually OVO agent username is LOCAL SYSTEM):



OVOserver# opcdeploy -cmd ‘osql -E -S TFORSELL\Inst1 -Q "select @@version"’ -node tforsell.pa.com

So, if the output of either of the above osql commands show some error, then it is not DBSPI fault, but instead a DBA problem (config error or access privilege problem).

---

In summary, if there are any errors from the OSQL command, then it is a DBA task to fix the configuration or authentication.

However, if the output shows nicely the MS SQL version strings like below, then it is something to do with DBSPI:



Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)

Feb 9 2007 22:47:07


Copyright 1988-2005 Microsoft Corporation

Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

So next we must check some important DBSPI file versions