Error messages in SBO 2007A

Is there a table in SBO 2007A where I can see recent error messages for all users?

Those error messages are saved under Log folder under B1 client one by one.  There is no table to hold all users' error messages
Thanks,
Gordon

Similar Messages

  • Error Stored Procedure Upgrading database from SBO 2007A PL42 to SBO 8.8

    Hi,
    When executing the SBO 8.8 PL00  upgrade procedure for databases for an "old" database 2007A PL 42, upgrtade stops whith an error concerning a missing stored procedure "_TmSp_CorrectWrongDocLineNumberInOINMForIPF which is not found".
    The error details says that it occurs on "Stock Updates" step (just after Checks for Payment) and log file gives the following message here after.
    Does anybody have an idea how to upgrade the 2007A database ?
    Thanks
    Error message in log :
    Upgrade          Error              Technical     Failed to call Stored Procedure TmSpCorrectWrongDocLineNumberInOINMForIPF
    Edited by: Michel Diepart on Oct 24, 2009 10:55 PM

    Hi Paul,
    Thanks for your prompt response on a saturday and so late in the evening
    Concerning the Stored Procedure, I would like to delete it but ... it doesn't exist and that's the problem...
    No such procedure in my database (programmability / Stored procedurefolder in SQL).
    When searching on the forum about this stored procedure, no result.
    Does this stored procedure have a link with something regarding adjustment in stock ?
    "Stock updates" : what table is it in SAP B1 ? If necessary I could save the table, create a sql query to re-create it after delete and try to restart the upgrade procedure but I don't know what is the related table...
    I will also try with another 2007A PL 42 database to see if it works.
    Do you know if anybody has already try to upgrade a 2007 PL42 dabase to SBO 8.8 ?
    Best regards

  • Error  Connection SBO 2007A PL 49 using Citrix MPX Version 4

    Dear All,
    I have some problem connection. We use Citrix for connection to SBO 2007A PL 49. When we through  Citrix Connection, the SBO Menu appears then show error message:Application has problem. Diagnostic file C:\Program FIles\SAP\SAP BUsiness One\Log\SAP Business One_20090907170137.dmp was created.
    We use Citrix MPX Version 4 and  Windows Server 2000.
    Please give me the solution ASAP. Because, the user can not do the transaction because of this.
    Thank you for your kind attention.
    Regards,
    Fitri

    Hi Fitri,
    There are various reasons why the error happened.
    You should create a support message to SAP and attach these 2 files:
    1.  SAP Business One YYYY MM DD HH MM SS.DMP.
    2.  SAP Business One YYYY MM DD HH MM SS_dyagnostic.TXT.
    from the  :Program Files\SAP\SAP Business One\Log
    Regards,
    David

  • XL Reporter Runtime error - upgraded from SBO 2005A to SBO 2007A

    Hi Experts,
    We upgraded our client SBO 2005A to SBO 2007A. We have this issue with XL Reporter that everytime we go to Advanced Report Builder-> Cell -> Transaction Row -> Attribute ->ARP_Series we are getting IXSelectionBarctl error window that says Run-time error '0', and the only option you have is OK. After pressing OK, it returns another IXSelectionBarctl window error:
    Run-time error '-2147418105 (80010007)'
    Automation error
    the callee (server (not server application) is not available and disappeared; all connection are invalid. The call may have executed.
    After pressing OK button the Advanced Report Builder is still visible but no longer accessible.
    Here is the command under Attribute I'm trying to access.
    "FIG( SO_DocDate = @d1:@d2 And ARP_Series = "1" ) ARDT( Code = "Invoice" )"
    Also, this report does not display the item quantity recorded in the invoice. It returns no data when running the report.
    I think the problem is that the ARP_Series is no longer available in 2007A, if not where do I find the series or somewhat similar to ARP Series function?
    Any help will be greatly appreciated.
    Thank you!

    Please check this thread:
    Unable to connect XL Reporter in 2007 B
    Thanks,
    Gordon

  • SAP B1 2007A 00 PL49- Error message 130-4 your software version is not upda

    Hi can somebody help how to solve this problem. When upgrading to SAP B1 2007A 00 PL49 I get error message:
    Your software is not updated error 130-4

    Hi,
    You must check if your database is not upgraded to previous PL of SAP 2007A.
    I suggest to upgrade your B1 db to 2007A SP01 PL05
    JimM

  • SBO Integration Service Error message

    When entering into SBO 8.81 i get the next error mesage. I tried and made test of everything and is ok.
    I got the next error SBO Integration Service authentication failed. Log off from the aplication; then log on and try again. If the problem persists, contact your system administrator.
    Any suggestion ?

    Would be interested to know if this ever got resolved as am seeing the same thing on my install -
    W2008 server foundation R2 64bit
    SQL 2008
    SAP 8.81 PL06
    Installed using B1iadmin username when prompted. Tried using B1i as had been advised and the install failed. Tried again using B1iadmin and install returned no errors.
    Configured the landscape using local SQL settings - worked fine, configured remainder using B1iadmin and tested connection - worked fine. Tried with B1i and wouldn't even connect to the server.
    within B1, am unable to swap license allocation between B1i and B1iadmin as keeps reverting back to license being issued to B1i.
    only exterior symptom though is the error message reported regarding authentication

  • SBO 2007a -  oInventoryGenEntry .Add()   Error -5002

    We convert the com-DI to work with the new SBO 2007a after upgrading and this code only stop to
    work and return -5002
    m_InternalDocObj is of type SAPbobsCOM.BoObjectTypes.oInventoryGenEntry
    :(here is the code...)
    'region document -add data
    MyBase.m_InternalDocObj.CardCode = ""
    MyBase.m_InternalDocObj.DocTotal = 1
    'Document_Lines is a child object of Documents object and represents the line entries of a
    document in the Marketing Documents and Receipts module
    'and the Inventory and Production module.
    'Region(oInvGenEntry.Lines) - add data
    MyBase.m_InternalDocObj.Lines.ItemCode = itemCode
    MyBase.m_InternalDocObj.Lines.AccountCode = ""
    MyBase.m_InternalDocObj.Lines.ItemDescription = ItemDescription
    MyBase.m_InternalDocObj.Lines.WarehouseCode = WHcode '
    MyBase.m_InternalDocObj.Lines.Currency = Currency 
    MyBase.m_InternalDocObj.Lines.Price = GRTotalPrice
    MyBase.m_InternalDocObj.Lines.Quantity = SerialsQuantity
    For i = 0 To SerialsQuantity - 1
    ManufacturerSerialNumber = ManufacturerSerialNumber + i
    MyBase.m_InternalDocObj.Lines.SerialNumbers.ManufacturerSerialNumber =
    ManufacturerSerialNumber.ToString() 
    MyBase.m_InternalDocObj.Lines.SerialNumbers.InternalSerialNumber = ""
    MyBase.m_InternalDocObj.Lines.SerialNumbers.BatchID = BatchID
    MyBase.m_InternalDocObj.Lines.SerialNumbers.Notes =
    ManufacturerSerialNumber.ToString()
    MyBase.m_InternalDocObj.Lines.SerialNumbers.Location = ""
    ' The last Lines.SerialNumbers should not used Lines.SerialNumbers.Add()
    If i = SerialsQuantity - 1 Then
    Else : MyBase.m_InternalDocObj.Lines.SerialNumbers.Add()
    End If
    Next
    m_iErr = MyBase.m_InternalDocObj.Add()  - Error ocured here -5002
    thanks in advance
    yaniv

    Hello,
    So,
    Please decide whihc serial number type you are using
    Only the First Row of Serial Numbers collection is not necessary to use the Lines.SerialNumbers.Add()
    So,
    For i = 0 To SerialsQuantity - 1
    ' add a new lines to Serial numbers collection
    if i > 0 then Lines.SerialNumbers.Add()
    Lines.SerialNumbers.SetCurrentLine(i)
    ' Check the AdministrationSystem Init .. General SettingsInventory TAB for Unique Serial Number type...
    ManufacturerSerialNumber = ManufacturerSerialNumber + i
    MyBase.m_InternalDocObj.Lines.SerialNumbers.ManufacturerSerialNumber =
    ManufacturerSerialNumber.ToString()
    MyBase.m_InternalDocObj.Lines.SerialNumbers.InternalSerialNumber = ""
    ' Not Needed MyBase.m_InternalDocObj.Lines.SerialNumbers.BatchID = BatchID
    MyBase.m_InternalDocObj.Lines.SerialNumbers.Notes =
    ManufacturerSerialNumber.ToString()
    MyBase.m_InternalDocObj.Lines.SerialNumbers.Location = ""
    ' The last Lines.SerialNumbers should not used
    'not needed If i = SerialsQuantity - 1 Then
    'Else : MyBase.m_InternalDocObj.Lines.SerialNumbers.Add()
    'End If
    Next
    Regards
    János

  • SBO Installation error message.

    Hi all,
    Sorry but this is not an SDK specific question!
    I am trying to install SBO 6.5 on a Windows XP laptop for demo purposes (first time install) - it is giving me an error message saying "could not create database" during the install. I came across this before and it was related to a problem with SQL Server/MSDE. MSDE was installed on the laptop but I feel it isn't installed properly (it does not show up in the Add/Remove Programs list). There is also a folder called C:\Program Files\Microsoft SQL Server\MSSQL$MicrosoftBCM on the laptop (Microsoft Business Contact Manager?) which maybe stopping MSDE from installing correctly? (This folder has several subfolders one of which is called Data that contains the master.mdf sql database and its associated files etc).
    Has anyone come across this problem before or have a solution to it?
    Thanks in advance.
    Regards,
    Andrew.

    I have seen the 'could not create database' message a few times during SBO installs before.  It has always been when an old copy of the Common or Demo databases has been left behind on the disk.
    You can easily check to see if it is this problem by using either osql (select name from sysdatabases) or searching using windows explorer to find the MDF files.
    If that is the problem then use Enterprise manager / osql / windows explorer to remove the database files.
    Another possibility at SQL Server might be the default data file location pointing to a non-existant folder.  You can check this setting in enterprise manager, or just try manually creating a new database to see if the problem exists.
    John.

  • Upgrading SBO 2005A SP 01 PL 29 to SBO 2007A PL 00

    Dear All,
    I've heard that SBO 2005A SP 01 PL 29 could be upgraded to latest PL of SBO 2007A after upgraded into PL 00 of SBO 2007A. This info is hopefully useful.
    Rgds,

    Hi Jimmy and William,
    I think there's a slight, but important misunderstanding - and I suspect that William may not have revisited this discussion:
    Error importing oBusinessPartners with DTW 2005.0.16
    ...but that's no severe enough to get so upset, Jimmy, or?
    Just to recap that:
    SAP Business One 2005A SP01 <b>PL22</b> is the last patch that you can apply before upgrading to SAP Business One 2007A <b>if</b> you want to participate in <b>Ramp-Up for B1 2007</b>!
    ...and currently you can only use B1 2007 - and get support from SAP when your customer IS <u>accepted</u> for the Ramp-Up!
    Only <b>after</b> SAP Business One 2007A will go into <b>"general availablility"</b> this would change!
    The upgrade paths for B1 2007 are as you described:
    - Upgrade from any patch of an older release to a newer version using the specific <b>Upgrade</b> package is possible - and supported.
    The "Upgrader" package is actually a patch that has been validated / released to be used for any upgrades from older versions.
    - Direct Upgrades to later patches of the newer version (skipping the Upgrader) may technically work at first glance, but you can't be sure that no issues may occurr later - and in the end cost more time than you gained by overstepping one step in the upgrade process - and it may get you in "trouble" with SAP Support.
    I am sorry, but I didn't phrase that correctly when I entered that comment!
    But again, unless you are getting this customer into Ramp-Up for 2007 it is irrelevant for you anyway what patch from 2005A SP01 you are using now...
    BTW: I have checked the statement on SAP Service Marketplace - and maybe this can be clarified even better too.
    Thanks for raising this question!
    Regards,
    Frank
    Message was edited by:
            Frank Moebius

  • Error Message : Unable to load DLL (AddOnInstallAPI.dll)

    Hi there..
    I am lost in SBO Installation I have made an installation package for my add-on. When I want to deploy for my client, i get a very silly Microsoft .Net Framework error message, that is :
    Unable to load DLL (AddOnInstallAPI.dll)
    Here is my function to call the .dll file:
    Private Sub Install()
      Environment.CurrentDirectory = strDll
      Dim sInstaller As String = installerPath
      'installerPath is path for my Setup.exe file
      Try
         'Run a new process
         System.Diagnostics.Process.Start(sInstaller)
      Catch ex As Exception
         MsgBox(ex.Message)
         Windows.Forms.Application.Exit()
      'Loop until windows found the executables   
      While System.IO.File.Exists("C:\Program  Files\MyCompany\Statement of Account\SOA.exe") = False
      End While
      'After found the executables, then call SetAddOnFolder
      SetAddOnFolder("C:\Program Files\MyCompany\Statement of Account")
       EndInstall() ' Inform SBO the installation ended
       Windows.Forms.Application.Exit() ' Exit the installer
    End Sub
    Does anybody ever face the same problem? My Client are using SBO2004 P9. I created all my addon using SDK P23. Is there any effect using different patches?
    Just for your information, I try to uninstall everything, and re-install SBO2004A Patch 9 in my computer (same as my client) and it works fine!! Are there any other possibilities???
    Hopefully, somebody can help me...
    Thanks alot...

    yes, i put the correct strDLL string as the parameter. I am able to run the AddOnInstaller with my PC (SBO 2004A Patch 26) and I also did the installer using my PC.
    My Problem is that i can not to install in my customer PC which is using SBO2004A Patch 9.
    Does anybody has some ideas about this issue?
    Thanks for helping...

  • Error Message in Delivery : Quantity falls below minimum inventory level

    Version : SBO 2005 A SP01 PL22
    Description of Issue:  When trying to Add a Delivery you get Error Message: Quantity falls below minimum inventory level [Delivery - Rows - Warehouse Code] [line: 0]  [Message 131-14].  You are then unable to Post the Delivery and Print the corresponding Packing List.
    Testing Findings:  Upon detailed testing of this issue and work with SAP Support it has been determined that the issue is that the Delivery Row Ordered Qty is looking at the OITM In Stock Qty when determining if the full Row Qty can ship instead of the OITW In Stock Qty.  This is an issue because due to other "bugs" this Client has encountered their OITW Qtys in other Whses are negative, even though they have the Block Negative Inventory and the Manage Inventory by Warehouse Flags Checked On.  This then reduces the OITM Qty below the level of the Delivery Row and you get the above error message. 
    Example:  A Sales Order Row has an Order Qty of 15 for Whse 01 for a particular Item.  The OITW In Stock Qty for Whse 01 = 17.  The OITW In Stock Qty for Whse 03 = -7.  The Block Negative Inventory and Manage Inventory by Whse Flags are both Checked On.  The 'Net' OITM In Stock = 10.  When you try to Copy the Sales Order to a Delivery and Add the Delivery, you get the above Error Message and it will not allow you to Post the Delivery and Print the Packing List.
    Current Workaround:  Client is performing Inventory Goods Receipts to bring the In Stock Qtys in the affected Whses to greater than or equal to zero.
    Proposed Solution:  SAP Development to add logic to SAP Business One to validate the Delivery Row Qtys to Ship against the OITW In Stock Qtys instead of OITM when the Manage Inventory by Whse Flag is checked on. 
    Supporting Documentation: This DRQ Request relates to Support Message # 864405 2007.  All above referenced testing details including example SO#'s, Item #'s, etc. and an entire copy of the Client's database are available and linked to this Message #.

    Hi Ramu,
    also you can  make sure you are choosing the right WH in ctrlshiftS windows if You do, then chek on Inventory -> Inventory report -> inventory status if you have enought and available quantities for the delivery, if you dont then you gonna have to make the PO and the AP Invoice to add more quantity to that item
    regards

  • Error Message while converting the PO to A/P Invoice

    Hi,
    We use Business one 2007A. One of the users is getting the error message that says "Object reference not set to an instance of an object" while adding the A/P invoice.
    As a super user, I am able to add the invoice.
    Can someone tell me what this issue is?
    Thanks

    Hi,
    You may check "Object Reference Not Set To An Instance Of An Object"
    Thanks,
    Gordon

  • Error Message while adding Item in Item Master Data- [Microsoft][SQL Server Native Client 10.0][SQL Server]Conversion failed when converting the nvarchar value 's008 01' to data type int. (CINF)

    Dear Experts
    I am getting the following error message while adding item in Item Master data. I have modified the following SBO_SP_transactionNotification in SQL server after that could not able to add the item
    ALTER proc [dbo].[SBO_SP_TransactionNotification]
    @object_type nvarchar(20),                      -- SBO Object Type
    @transaction_type nchar(1),               -- [A]dd, [U]pdate, [D]elete, [C]ancel, C[L]ose
    @num_of_cols_in_key int,
    @list_of_key_cols_tab_del nvarchar(255),
    @list_of_cols_val_tab_del nvarchar(255)
    AS
    begin
    -- Return values
    declare @error  int                       -- Result (0 for no error)
    declare @error_message nvarchar (200)           -- Error string to be displayed
    select @error = 0
    select @error_message = N'Ok'
    --    IF @OBJECT_TYPE = '59' AND (@TRANSACTION_TYPE = 'A' or @TRANSACTION_TYPE = 'U')
      BEGIN
       IF EXISTS(
        SELECT T0.Price FROM IGN1 T0
        where  IsNull(T0.Price, '0') = '0' and T0.DocEntry = @list_of_cols_val_tab_del)
       BEGIN
        SELECT @ERROR=1,@ERROR_MESSAGE='Please insert the price !'
      END
    end
    -- Select the return values
    select @error, @error_message
    end

    Hi Rathna,
    Just put the SP like this, without the -- before the IF. A -- marks the line as a command therefore you need to uncomment and it will work.
    IF @OBJECT_TYPE = '59' AND (@TRANSACTION_TYPE = 'A' or @TRANSACTION_TYPE = 'U')
      BEGIN
       IF EXISTS(
        SELECT T0.Price FROM IGN1 T0
        where  IsNull(T0.Price, '0') = '0' and T0.DocEntry = @list_of_cols_val_tab_del)
       BEGIN
        SELECT @ERROR=1,@ERROR_MESSAGE='Please insert the price !'
      END
    end
    Hope it helps

  • Error message when logging in to SAP B1

    Hello,
    Does anybody have a clue, on that error message when I'm trying to
    log in to SAP B1: Invalid column name 'AppTime' ?
    I cannot log in to SAP B1, the error message appears (from MSSQL server),
    immediately after typing username/password and clicking OK on the log on
    window.
    Thank you,
    Balazs

    Hi,
    You can easily verify by yourself that no column AppTime exists in a standard B1 installation (just tested on 2007A SP01 PL6).
    You should have a reference to an external database or extension (addon)...
    What addons are you using?
    Regards,
    Eric

  • SQL Server 2005 Error Message - when Right Clicking a DB Properties

    Hi
    We are running SQL Server 2005 SP03, we have x15 databases (excluding SBO-COMMON, RSP, Coresuite), all x15 databases have Maintenance Plans setup, tasks ticked:
    - Shrink Database
    - Clean Up History
    - Back up Database (Full)
    - Maintenance Clean-up task
    These Maintenance Plans have been running for over 5 months now, we have recently changed our VMware Virtual Server over to a Hosted VMware Virtual Server, now when I right click on a certain database and select "Properties" I get the following error message with SQL Server:
    Property Owner is not available for Database '[Turquoise_Moon_Live]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights.  (Microsoft.SqlServer.Smo)
    Could the Maintenance Plan be preventing me to run the Properties against a relevant DB (I have tested this by restoring a DB that doe not have a Maintenance Plan and the Properties works, tested this on SBO-COMMON and it works as well)
    Can anyone agree with me or let me know what else might be the issue as I have checked the Server Roles & the Users Credentials for SQL and all seems well.
    Regards
    Kurt Walters

    Hi Gordon
    This solution did not work, but I needed to delete the Maintenance Plans anyway to set it for 1 month instead of 2 Months. I am thinking as we have changed Domains, were the last one was IS Domain and the new one is Hosted Domain, the security issues are probably coming from this (as I am able to access the Properties of the IS Domain SQL Server even with the Maintenance Plans running).
    Any thoughts on correcting this as we have changed Domains? (I have created a user as HOSTED\example, the old one was IS\example)
    Regards
    Kurt Walters

Maybe you are looking for