cancel
Showing results for 
Search instead for 
Did you mean: 

error in sap b1

Former Member
0 Kudos

hi friends,

   while i am log in the manager user in the server i am getting below error. it is happen only server

"[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot insert the value NULL into column 'logInstanc', table 'SBO_MAGNA_LIVE.dbo.AUSR'; column does not allow nulls. INSERT fails. '' (AUSR)"

is it make any problem????

Accepted Solutions (1)

Accepted Solutions (1)

KennedyT21
Active Contributor
0 Kudos

Hi Ramesh

Check this

1653119  - Error when update or logon into the application

Symptom  

1. When  you try to update any information in any Business One (B1) object you get an error 'This Entry Already Exists in the Following Tables "(AXXX)(ODBC - 2035) [ Message131-183]'.
2. One or more users try to connect to SAP Business One and get the following error message:

[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot insert the value NULL into column 'logInstanc', table '[DATABASE_NAME].dbo.AUSR'; column does not allow nulls. INSERT fails. '' (AUSR)

 

Cause

Application error

The log instance field in the history tables of all Business One objects is a 16-bit integer field with maximum value 32767. Every time the object is changed, a record will be written to the history table with the log instance number increased by 1. Hence if the object is changed too frequently, the log instance number will exceed the upper limit of the 16-bit integer field and overflow. This probably happens when you are using some add-ons which change the B1 object automatically.

 

Solution

SAP intends to provide a patch or patches in order to solve the problem described.

The section Reference to Related Notes below will list the specific patches once they become available.

The corresponding Info file of the patches in SAP Service Marketplace will also show the SAP Note number.

Please note that these references can only be set at patch release date.

SAP will deliver patches only for selected releases at its own discretion, based on the business impact and the complexity of the implementation.

   

       

Header Data

  
Released On 15.11.2011 12:56:17   
Release Status Released for Customer   
Component SBO-BC System   
Priority   Correction with medium priority   
Category   Program error   

  

      

References

This document refers to:

  SAP Business One Notes

1596532 Cannot insert the value NULL into column 'LogInstanc'

This document is referenced by:

   SAP Business One Notes (4) 

  1681770   Overview Note for SAP Business One 8.81 patch 11
  1596532   Cannot insert the value NULL into column 'LogInstanc'
  1660887   Overview Note SAP Business One 2007 A SP01 PL 17
  1665806   Overview Note for SAP Business One 2007 B Patch 26

Answers (3)

Answers (3)

kothandaraman_nagarajan
Active Contributor
0 Kudos

Hi Ramesh,

This is issue fixed in 8.81  PL11. Please refer SAP note 1653119

Thanks & Regards,

Nagarajan

kedalenechong
Participant
0 Kudos

Hi Rocio and Nagarajan

Thanks so much for your sharing of answers.

Former Member
0 Kudos

Hi,

What is your B1 version and PL? You may upgrade to a new version to avoid such error.

Thanks,

Gordon

Former Member
0 Kudos

Sap b1 8.8  PL12

KennedyT21
Active Contributor
0 Kudos

Hi Ramesh Kannan...

Follow the note to solve the issue . before  back up your database and try in test first

1587308  - User's login counter reset

Purpose

  According the current system definition every connection to the SAP Business One database cumulate the
LogInstanc counter in the AUSR table per user bases. Some customer’s solution might cause an overflow of
the integer number, which is defined for the LogInstanc field.

 

Actions

  The task will verify whatever the max(logInstanc) value in the AUSR table is greater than value 29000.
If the value is lower, then no action will be taken.
If the vale is greater or equal, then the task will fix the issue.

 

Impact on System

  Business One 8.8. and 8.81.

   

       

Header Data

  
Released On 03.07.2011 06:59:17   
Release Status Published     
Priority   Medium   
Category   DB Maintenance   
Product Version

SAP Business One 8.8

SAP Business One 8.81

Database

MSSQLSRV 2005

MSSQLSRV 2008

MSSQLSRV 2008 R2

  

      

Attachments

File Name

File Size (KB)

Mime Type

User's login counter reset.xml

11768

text/xml

Hope this will solve

Regards

Kennedy

Former Member
0 Kudos

Hi,

i have the same problem in SAP B1 8.81 (8.81.317) PL: 09.

Thanks.

kedalenechong
Participant
0 Kudos

Hi all

Is there any solution to this error message or we just ignore it?

One of our clients also encounter the same error message in the System Messages Log everytime logging into one specific database whether in SAP Server or client workstation even using manager super user login though it is not affecting any posting.

“[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot insert the value NULL into column 'logInstanc', table 'SBO_PAZIA.dbo.AUSR'; column does not allow nulls. INSERT fails. '' (AUSR)”

It gives the same error when we try edit User Authorization for one of the non superuser sap users login ID and it not possible to edit that User Authorization for that user only.

The SAP Business One version is 8.8 Patch 18 Hot Fix 1.

Former Member
0 Kudos

Hi Kedalene, i presented this problem after adding an addon,

the consultant that implemented the SAP in our company reached us a script to be run from time to time on the server.

The cause: A table of SAP log is not prepared for the amount of records that brings this addon and numbering exceeds the data type.

See it with your implementer, i enclose my script, but you should first consult with your implementer to be certain that what you use.

Atte.:

ENRIQUE VARGAS

REMICSA DRILLING SA

kedalenechong
Participant
0 Kudos

Hi Rocio

Thanks so much for your reply.

I have stopped and disconnected all AddOns but the same error message appears in system messages log.

By the way I can't find your script?

Can you send to kedalene@gmail.com?

kothandaraman_nagarajan
Active Contributor
0 Kudos

Hi,

This is issue fixed in 8.81  PL11. Please refer SAP note 1653119.

Note : Please check your Gmail.

Thanks & Regards,

Nagarajan

Former Member
0 Kudos

Hi Ramesh......

It seems something is internally damaged to the Database.

Is that happening when your any of the Addon is running?

Or is that happening to every client machine?

Regards,

Rahul

Former Member
0 Kudos

it is happening only server . while i open the sap b1 in the server it is happening. not happen in client machine. addon is  not running. i am running add-on only manual

Former Member
0 Kudos

it is happening only server . while i open the sap b1 in the server it is happening. not happen in client machine. addon is  not running. i am running add-on only manual