Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

W4104 - cannot update Database 1

Status
Not open for further replies.

trilog

IS-IT--Management
Aug 22, 2002
9
DE
We get the above error in our activity log under Arcserve 2000 SP3 every time Arcserve tries to update the Arcserve SQL Database with the newest tape information.

Our configuration is:

Arcserve Server:
Arcserve 2000 SP3
Windows 2000 Server SP2

SQL Server (different machine!):
SQL Server 2000 SP2
Windows 2000 Server SP2

Here is the error information from the Arcserve logfile:

20020822 045518 410 N5936 Folgender Datenträger kann in der Gerätegruppe GROUP0 für den nächsten Job am 22.08.02 verwendet werden:
20020822 045518 410 N5942 1. F-SFP00333-MI-14.08.02 [S/N:000044, NR:2] SFP00333_DLY
20020822 045518 410 N5942 2. F-SFP00333-DO-15.08.02 [S/N:000146, NR:1] SFP00333_DLY
20020822 045518 410 N5942 3. F-SFP00333-DO-15.08.02 [S/N:000063, NR:2] SFP00333_DLY
20020822 045518 410 N5941 4. <LEERES BAND>
20020822 045549 W4104 Datensatz kann nicht eingefügt werden. (FC = SQL Error State:22003, Native Error Code: 1FB3, ODBC Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Arithmetischer Überlauffehler beim Konvertieren von expression in den Datentyp int.SQL Error State:01000, Native Error Code: E25, ODBC Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Die Anweisung wurde beendet.)

Everybody's help is urgently needed!

Best regards
Patrick Stoffer
 
I have tracked down the error above to be a problem with the table &quot;astape&quot;. It occurs only if arcserve has used named pipes to read/write to any database before. (Exchange, SQL, and its own database pruning).

I hope, it is a little bit clearer now.

Thanks for help.

Best regards
Patrick Stoffer
 
Thanks to I was able to translate the error message you are getting. :cool:

This was fixed in T352003. It changed all the KB data fields (tape usage, etc.) to MB, and adjusts the reporting, displays, updates, etc. as such. It will not convert the existing data.

This problem existed with both VLDB and SQL databases.
 
Hi jabus,

many thanks for your answer.
Do you have this fix?
If it is so, please let me know how to install it, and where I can find it. Arcserve says, that it is an unsupported &quot;testfix&quot;, and the hotline refuses to give any further answers.

Best regards,

Patrick Stoffer
 
Our support agreement gives us access to these test fixes. I've never used the hotline, so I'm not sure of the procedure to get the fix. If you have a local client relationship manager, or salesperson, you might try that avenue.
 
BTW, unless you need to use those Usage fields, you can ignore this error. It will not affect your database, other than not being able to update those fields.

I hightly recommend getting some kind of support contract that will give you access to these test fixes, as there have been several relating to using SQL server as the database, engine crashes, etc.
 
Hi jabus,

many thanks for your answer.

May I ask to give me a detailed description of the patch and if possible the readme file. If it is possible, please let me known, if you are allowed to email this fix to me.

My emailadress is Patrick.Stoffer@trilogexpert.com

Best regards
Patrick Stoffer
 
That T-fix is dependant on another T-fix, which is dependant on yet another T-fix, etc. I don't know what our license is, and if these T-fixes can be distributed.

As a way to &quot;band-aid&quot; this issue for now, you can delete the Device records in ARCserve by opening ASMgr, go to the Database Manager, view the Device Records, and delete all the devices. Then stop and start the tape engine. Those records will be recreated.

If you view the Statistics (before deleting, obviously), you should see the &quot;KB&quot; Written to be >2 billion. This fix is to only write MB--they did not extend the length of the field, and it will have to be erased anyway.

Here are some lines from this fix. BTW, this is also a problem when using VLDB, but no error is ever reported. It was fixed, however, as there is a new asdbcli2.dll.

PRODUCT: ARCserveIT NT Advanced Edition RELEASE: 7.0-AE

PROB #: 488 FN: T352003 FT: CJ8 DATE: 22 May 2002
STARTRAK PRODUCT NAME: ARCSNT (Star Problem Product)

PROBLEM SYMPTOM: NT -SQL DATABASE ERRORS APPEAR IN THE ACTIVITY LOG
----------------------------------------------------
>>> ATTN: THIS FIX IS FOR NT 4.0/W2K ONLY <<<

>>> ATTN: APPLICABLE LANGUAGES <<<
ENGLISH
>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<


If ARCserve 2000 is setup to use SQL 7.0/2000 as
the database, the following error message may
appear in the activity log:

20020503 100207 [SQL]
_ASDBCliUsageTimeTapeDrv_70(rc=SQL Error
State:22003, Native Error Code: 1FB3, ODBC Error:
[Microsoft][ODBC SQL Server Driver][SQL
Server]Arithmetic overflow error converting
expression to data type int.SQL Error
State:01000, Native Error Code: E25, ODBC Error:
[Microsoft][ODBC SQL Server Driver][SQL
Server]The statement has been terminated.)


UPDATED ROUTINES:
---------------
asdbcli1.dll 380928 TUE MAY 21 18:42:43 2002
ASDBCLI2.dll 172032 TUE MAY 21 18:40:32 2002
Asm_db.dll 335872 WED MAY 22 11:20:56 2002
asm_rp.dll 344064 WED MAY 22 11:31:46 2002

 
Many many thenks to you, jabus.

I will try this, and I let you know, if it is ok.

Best regards
Patrick Stoffer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top