Error "-602" occurred in the current database connection "R/3*".

Hi All,
I am working with Preview 2004s ABAP Trial version ,when load data from PSA to Info cube with help of DTP , getting following error.
Runtime Errors DBIF_DSQL2_SQL_ERROR
Except. CX_SY_NATIVE_SQL_ERROR
Date and Time 20.07.2008 16:04:52
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error "-602" occurred in the current database connection "R/3*".
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
How to correct the error
Database error text........: "POS(1) System error: BD Index not accessible"
Database error code........: "-602"
Triggering SQL statement...: "INSERT INTO "/BIC/SZD_PROD" ( "/BIC/ZD_PROD",
"SID", "CHCKFL", "DATAFL", "INCFL" ) VALUES ( ? , ? , ? , ? , ? )"
Internal call code.........: "DBDS/NEW DSQL"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
please help me in this
Kind regards.
Hari

Hi All,
Problem resloved.
hari

Similar Messages

  • The error 600 occurred in the current database connection "LCA".

    Hi All,
    User is executing job /SAPAPO/TS_REALIGN_COPY in background,  as soon as the job is released its failing with runtime error:
    I check the Note 1126394 but not relevant.
    Runtime Errors         DBIF_DSQL2_SQL_ERROR
    Exception              CX_SY_NATIVE_SQL_ERROR
    Date and Time          18.08.2011 00:03:39
    Short text
         An SQL error occurred when executing Native SQL.
    What happened?
         The error 600 occurred in the current database connection "LCA".
    What can you do?
         Note down which actions and inputs caused the error.
         To process the problem further, contact you SAP system
         administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
         at and manage termination messages, and you can also
         keep them for a long time.
    How to correct the error
        Database error text........: "POS(1) Work rolled back: BAD_ALLOCATION in
         SAPTS_COPY_DA"
        Database error code........: 600
        Triggering SQL statement...: "EXECUTE PROCEDURE SAPTS_COPY_DATA"
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "DBIF_DSQL2_SQL_ERROR" "CX_SY_NATIVE_SQL_ERROR"
        "/SAPAPO/SAPLOM_TIMESERIES" or "/SAPAPO/LOM_TIMESERIESU20"
        "/SAPAPO/OM_TS_DATA_COPY"
        If you cannot solve the problem yourself and want to send an error
        notification to SAP, include the following information:
        1. The description of the current problem (short dump)
           To save the description, choose "System->List->Save->Local File
        (Unconverted)".
        2. Corresponding system log
           Display the system log by calling transaction SM21.
           Restrict the time interval to 10 minutes before and five minutes
        after the short dump. Then choose "System->List->Save->Local File
        (Unconverted)".
    Information on where terminated
        Termination occurred in the ABAP program "/SAPAPO/SAPLOM_TIMESERIES" - in
         "/SAPAPO/OM_TS_DATA_COPY".
        The main program was "/SAPAPO/TS_RLG_COPY_SINGLE ".
        In the source code you have the termination point in line 57
        of the (Include) program "/SAPAPO/LOM_TIMESERIESU20".
        The program "/SAPAPO/SAPLOM_TIMESERIES" was started as a background job.
        Job Name....... "/SAPAPO/TS_REALIGN_COPY"
        Job Initiator.. "CIBERNLAPO2"
        Job Number..... 00015100
        The termination is caused because exception "CX_SY_NATIVE_SQL_ERROR" occurred
         in
        procedure "/SAPAPO/OM_TS_DATA_COPY" "(FUNCTION)", but it was neither handled
         locally nor declared
        in the RAISING clause of its signature.
        The procedure is in program "/SAPAPO/SAPLOM_TIMESERIES "; its source code
         begins in line
        1 of the (Include program "/SAPAPO/LOM_TIMESERIESU20 ".
    Kindly suggest any notes or is any setting needs to be modified.
    Regards,
    Kaasi

    Hello Ada,
    the job was aborted due:
    Database error text........: "POS(1) Work rolled back: BAD_ALLOCATION in 
         SAPTS_COPY_DA"
        Database error code........: 600
        Triggering SQL statement...: "EXECUTE PROCEDURE SAPTS_COPY_DATA"
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
    From the posted dump.
    Was it lack of OMS heap memory, memory leaking, program error or huge data selection for application run it's not clear. It will be best for SAP customer to create the SAP message and get SAP support when application canceled due Database error BAD_ALLOCATION in  LCA routine.
    Regards, Natalia Khlopina

  • The error "-10401" occurred in the current database connection "LCA"

    Hi everyone,
    I installed livecache 7.7 with scm7.0,when i did postinstallation  Initialization or run t-code lca03,i got error dump as below.now the livecache states is good.in scm server I not installed package Lcapps.please help give your advise,thank you so much.
    untime Errors         DBIF_DSQL2_SQL_ERROR
    xception              CX_SY_NATIVE_SQL_ERROR
    ate and Time          01/20/2010 03:26:32
    Short text
        An SQL error occurred when executing Native SQL.
    What happened?
        The error "-10401" occurred in the current database connection "LCA".
    How to correct the error
        Database error text........: "Conversion of parameter/column (1) would tru
         data"
        Database error code........: "-10401"
        Triggering SQL statement...: "EXECUTE PROCEDURE "APS_PLAN_VERSION_GET""
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:

    Hi Natalia,
    thanks for you much help,the livecache version is 7.7.02,so I will try to upgrade to 7.7.04,thank you.
    Server Utilities    d:/sapdb/programs      7.7.02.08     64 bit    valid
    DB Analyzer         d:/sapdb/programs      7.7.02.08     64 bit    valid
    PCR 7301            d:/sapdb/programs      7.3.01.21               valid
    PCR 7500            d:/sapdb/programs      7.5.00.42     64 bit    valid
    SAP Utilities       d:/sapdb/programs      7.7.02.08     64 bit    valid
    APO LC APPS         d:/sapdb/k1p/db/sap    6.00.004      64 bit    valid
    Base                d:/sapdb/programs      7.7.02.08     64 bit    valid
    Redist Python       d:/sapdb/programs      7.7.02.08     64 bit    valid
    JDBC                d:/sapdb/programs      7.6.03.02               valid
    Messages            d:/sapdb/programs      MSG 0.5010              valid
    ODBC                d:/sapdb/programs      7.7.02.08     64 bit    valid
    SQLDBC 77           d:/sapdb/programs      7.7.02.08     64 bit    valid
    Database Kernel     d:/sapdb/k1p/db        7.7.02.08     64 bit    valid
    Loader              d:/sapdb/programs      7.7.02.08     64 bit    valid
    SQLDBC              d:/sapdb/programs      7.7.02.08     64 bit    valid
    Fastload API        d:/sapdb/programs      7.7.02.08     64 bit    valid
    SQLDBC 76           d:/sapdb/programs      7.6.01.15     64 bit    valid

  • The error "-10709" occurred in the current database connection "LEA"

    Hi,
    I've Updated forecast and I have the followoing error message,
    (/SAPAPO/MMSDP)
    Database error text........: "Connection failed (RTE:protocol error)"
    Database error code........: "-10709"
    Triggering SQL statement...: "EXECUTE PROCEDURE LCK_DEQUEUE_OWNER"
    Internal call code.........: "[DBDS/NEW DSQL]"
    Please check the entries in the system log (Transaction SM21).
    the error "-10709" occurred in the current database connection "LEA"
    just after it was ok .
    I knwo LEA is the lock table to the liveache, is there parametes tied to the lock (like R/3 enque/table...?)
    Does someone have an idea of this issue (which happened regulary for the first time this morning, we're SCM 5.0)
    Best Regards,
    John

    John,
    It looks like a support pack issue.
    Check this post, maybe it will help:
    the error "-10401" occurred in the current database connection "LCA"
    Let me know if this was helpful.
    Abhi

  • Error "-7500" occurred in the current database connection "LCA"

    LC & apo box rebooted due hardware failure now once LC is up then all cif quuese are failing with "An SQL error occurred when executing Native SQL" error. Looking further it indicates lc issue.
    Getting multiple dumps in apo box with :-
    Short text
        An SQL error occurred when executing Native SQL.
    What happened?
        The error "-7500" occurred in the current database connection "LCA".
    What can you do?
        Note down which actions and inputs caused the error.
        To process the problem further, contact you SAP system
        administrator.
        Using Transaction ST22 for ABAP Dump Analysis, you can look
        at and manage termination messages, and you can also
        keep them for a long time.
    How to correct the error
        Database error text........: "POS(1) DCOM HRESULT:APS_COM_VERSION_GET,00000002"
        Database error code........: "-7500"
        Triggering SQL statement...: "EXECUTE PROCEDURE "APS_COM_VERSION_GET""
        Internal call code.........: "[DBDS/NEW DSQL]"
        Please check the entries in the system log (Transaction SM21).
    Steps already taken :-
    1) LC apps start/stop
    2) Index recovery done from DBMGUI
    Any suggestion on this ? Only expert comments please.

    >
    > Steps already taken :-
    > 1) LC apps start/stop
    did you restart liveCache from LC10 -> administration-> ...?
    -any errors in lcinit.log ? (/sapdb/data/wrk/)
    -any errors in knldiag or knldiag.err
    -I would suggest to open SAP message and let them to login and check it
    Regards
    Ivan

  • An internal database error occurred in the Business Data Connectivity Shared Service. SQL Error Number : 229

     Recently i upgraded my SharePoint server 2013 to SP1, after the upgrade i received following message in manage database Status page " Databases running in compatibility range, upgrade recommended" 
    for Business Data Connectivity Database. Then i ran Sharepoint Configuration wizard, which fixed that error on that page but i am getting a error message while accessing BDCApplication page in manage service applications pagein central admin"
    An internal database error occurred in the Business Data Connectivity Shared Service. SQL Error Number : 229
    Sys Log :
    The BDC Service application failed due to a SQL Exception: SQLServer host WSQLD05\DV. The error returned was: 'The EXECUTE permission was denied on the object 'proc_ar_GetAdministrationMetadataCatalogByPartitionId', database 'sp_BusinessDataConnectivity_DV13',
    schema 'dbo'.'
    I checked the Db role of the service app pool account, it has SPDataAccess permission over the Database. i cant recreate another application without knowing the root cause. I hope i can get better option to troubleshoot the issue.
    Thank you

    As per the error message, you can at least grant the BDC service application pool account the EXECUTE perimssions on the sp_BusinessDataConnectivity_DV13 database
    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog |
    Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course

  • MS SQL server is going down frequently(10 days of gap) with exception message: "A severe error occurred on the current command. The results, if any, should be discarded".

    MS SQL server is going down frequently(10 days of gap) with exception message: "A severe error occurred
    on the current command. The results, if any, should be discarded". We are facing this issue for past two month.But funny thing is server will be up automatically with out any service restart manually.  Also if we try to restart the SQL
    server service manually then SQL server will be in a dead lock situation and it will not come up even if we wait for long time. Then we should do a windows server machine restart to
    make the SQL sever up. As a suggestion from Microsoft to fix this kind of similar issue,
    we have installed service pack 3 for SQL Server. But even after we are facing same issue.
    Server Details:
    Server OS: Windows Server 2008 R2
    Two type of database servers are installed on server:
    1. MS SQL Server 2008 R2
    2. My SQL
    Also Reporting server is configured for the purpose of generating SSRS report from a dot net website.
     NOTE:Immediately after the data retrieval/save, we are closing the connection explicitly by the
    application.
    we have checked the windows event log and below are the details:
    Log Name:      Application
    Source:        ASP.NET 4.0.30319.0
    Application information:
        Application domain: /LM/W3SVC/5/ROOT-1-130718142067856406
        Trust level: Full
        Application Virtual Path: /
        Application Path: E:\WebSpaceFolder\ACSQuiK\Production\
        Machine name: DBSERVER 
     Process information:
        Process ID: 148
        Process name: w3wp.exe
        Account name: NT AUTHORITY\NETWORK SERVICE 
     Exception information:
        Exception type: SqlException
        Exception message: A severe error occurred on the current command.  The results, if any, should be discarded.
       at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
       at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
    Log Name:      Application
    Source:        Report Server Windows Service (MSSQLSERVER)
    Description:
    Report Server Windows Service (MSSQLSERVER) cannot connect to the report server database.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Report Server Windows Service (MSSQLSERVER)" />
        <EventID Qualifiers="0">107</EventID>
    Could anybody can suggest any kind of fix for this issue? Thanks in advance.

    Hi YesYemPee,
    I have tried but still not clear about your issue, I would like you provide more details information about your issue based on below points to better analysis about the issue:
    What action did you do and caused the error "A severe error occurred on the current command. The results, if any, should be discarded", did you run report on the web application or something else then the error happen?
    If you rendering the report and got the error, please try to provide us more error information in the log files which path like:
    C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles
    If it is not the case in step1, Please try to provide SQL Server Error log(SQL Server Logs) and more details information.
    If you still have any problem, please feel free to ask.
    Regards,
    Vicky Liu
    Vicky Liu
    TechNet Community Support

  • A severe error occurred on the current command. The results, if any, should be discarded(Not Always)

    We have a DotNet website which is deployed on a physical server(windows server 2008 r2). The application is started to using for live. Most of the time application is  working fine. But some times we have noticed the application is failed to communicate
    with MS SQL 2008 R2 database and as result the below error is displaying:
    "A severe error occurred on the current command. The results, if any, should be discarded. at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject
    stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean&
    dataReady) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean
    enlistOK) "
    If we tried to connect the database server the same issue is showing:"A severe error occurred on the current command. The results, if any, should be discarded"
    The issue will be resolved automatically after 30-45 minutes .   Please let us know if any fixes can be done to resolve this issue.
    NOTE: We have installed SQL Server 2008 service pack 3 as per the suggestion from experts .But still the issue pwersist.

    Hello,
    When this issue occurs have you check the existing connections? If an app was unclean developed it can happen that the app opens connection by connection, but never closed them correctly and when all available connections are in use, such an error can occur.
    Olaf Helper
    [ Blog] [ Xing] [ MVP]

  • Unable to refresh the schema of FIM MA.Getting an error in Event viewer ""the current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of database is : 1116. The expected version is :1"

    Hi,
    We have installed FIM MA with an account that have all the sufficient rights.It got created successfully and worked for Full Import and Full Sync. But, due to some version incompatabilities, we have installed a patch.PFB link for the patch.
    http://support.microsoft.com/en-us/kb/2969673/en-us
    Now, we are trying to refresh the schema of FIM MA. While doing that we are facing an error "Failed to connect to database". The user account with which we are connecting has read and write permissions on DB.In the event viewer some errors are
    logged like  "the current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of database is : 1116. The expected version is :1122" with event ID 3. PFB images for more detailed
    view.
    Please advice how to fix the issue.
    Thanks
    Prasanthi.

    Hello,
    seems to me that you maybe only updated the syncengine but not portal/webservice.
    I had that error once after an recovery from scratch and forgot one of the hotfixes to apply to all services.
    -Peter
    Peter Stapf - ExpertCircle GmbH - My blog:
    JustIDM.wordpress.com

  • A severe error occurred on the current command - select into

    Hi
    I am making a backup of a table before working on the original, but when I try a simple select into statement I receive 'Msg 0, Level 11, State 0, Line 0 - A Severe error occurred on the current command.  The results, if any, should be discarded.'
    I am able to run a select query on the original table with the same where clause I am using in the select into statement and it runs without error.  
    Does anyone know why this is happening?
    Server 2008 64bit, SQL Server 2008r2
    Thank you for any help

    This is a generic message that informs you that something went very wrong, either in SQL Server itself or in the client API.
    If open a command promptt and try the same command running from SQLCMD or OSQL, what happens? If things seems to work well, run a simple second command like "SELECT 1" to make sure that this works. (The use a different API from SSMS, why it is
    worth testing.)
    Also look in the SQL Server error log. If you see a stack dump which appeared at the same time as you ran the SELECT INTO statement, then it's clear that the accident was in SQL Server.
    I would recommend that you run DBCC CHECKDB on the database, as the root cause could be corruption.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • A server error occurred on the current command. the results if any should be discarded in SQL 2008 R2

    Hi,
    I am using SQL server 2008 R2 and also MultipleActiveResultSet = true and Pooling = true (default value) in connection string.
    While executing query 'IF ORIGINAL_LOGIN() = SUSER_SNAME() EXECUTE AS USER = 'MyUser'', I received error stating  'A server error occurred on the current command. the results if any should be discarded'. At the same time I could check that SqlConnection
    state is also closed.
    I have also fired 'REVERT' query If I find such exception and again try to execute same query again. but no luck. I received the same exception while executing query (Execute As) again.
    What can be the solution to avoid such exception and make my code working?
    Thanks,
    Ashish

    Login failed for user 'sa'. The user is not associated with a trusted SQL Server connection.
    Above issue occurs genrally when authentication mode is set to Windows Authentication insted Mixed Mode.
    You can change the authentication mode of the SQL server from “Windows Authentication Mode (Windows Authentication)” to “Mixed Mode (Windows Authentication and SQL Server Authentication)”.
    Run following script in SQL Analyzer to change the authentication
    LOGIN sa ENABLE
    GO
    ALTER LOGIN sa WITH PASSWORD = '<password>'
    GO
    http://blog.sqlauthority.com/2007/04/14/sql-server-fix-error-18452-login-failed-for-user-null-the-user-is-not-associated-with-a-trusted-sql-server-connection/
    But as per the first post it seems issue is different have you observerd Error log?
    Check out at C:\Program Files\Microsoft SQL Server\MSSQL.n\MSSQL\LOG\ERRORLOG
    Location might differ as per the Server configration
    Please click the Mark as answer button and vote as helpful if this reply solves your problem

  • A severe error occurred on the current command. The results, if any, should be discarded.

    I have a strange situation on a database, which are on SQL Server 2008 R2 Express SP2. The database size is something around 90 MB.
    When a user try to insert a record inside one table, he receive an error message,  and the program is disconnected from the database. I tried to investigate this issue, and I discovered that when user try to insert one row  the trigger for
    insert invoke also the trigger for update and sql server crushes with "A severe error occurred on the current command.  The results, if any, should be discarded."
    I have checked from SQL Server Management Studio to run a direct Update on the specific table. The same error occurred.
    I have run DBCC CheckTable and no errors have been found. I also have run DBCC CHECKDB and no errors.
    Because I also have 3 other different databases, with the same functionality, on the same server which are going well with more than 100 000 records in that specific table, and the triggers are going well for more than 5 years, I have assumed that some
    problems occurs inside the database. That is why I have copied all the records from the "damage" database to a new one. This means that inside the new databases the indexes are regenerated and a new space will be allocated.
    The same strange things are happening. The same table can not be updated with a very basic Update statement.
    I am looking for a patch or KB to solve this issues.
    Any ideas are will be appreciated.
    Thank you

    there is a file as response to one of my tests to investigate which command is responsible for this error. 
    Current time is 21:18:39 08/18/13.                                                                              
    =====================================================================                                           
           BugCheck Dump                                                                                            
    =====================================================================                                           
    This file is generated by Microsoft SQL Server                                                                  
    version 10.50.4000.0                                                                                            
    upon detection of fatal unexpected error. Please return this file,                                              
    the query or program that produced the bugcheck, the database and                                               
    the error log, and any other pertinent information with a Service Request.                                      
    Computer type is Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz.                                               
    Bios Version is INTEL  - 1072009                                                                                
    BIOS Date: 09/23/09 11:58:43 Ver: 08.00.10                                                                      
    8 X64 level 8664, 2 Mhz processor (s).                                                                          
    Windows NT 6.1 Build 7601 CSD Service Pack 1.                                                                   
    Memory                              
    MemoryLoad = 16%                    
    Total Physical = 8125 MB            
    Available Physical = 6755 MB        
    Total Page File = 16248 MB          
    Available Page File = 14719 MB      
    Total Virtual = 8388607 MB          
    Available Virtual = 8380163 MB      
    ***Stack Dump being sent to d:\MSSQL10_50.MSSQLSERVER\MSSQL\LOG\SQLDump0084.txt                                 
    SqlDumpExceptionHandler: Process 52 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is
    terminating this process.                                                                                       
    * BEGIN STACK DUMP:                                                                                             
    *   08/18/13 21:18:39 spid 52                                                                                   
    *   Exception Address = 0000000000886B00 Module(sqlservr+00000000001F6B00)                                      
    *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION                                                     
    *   Access Violation occurred writing address 0000000000000000                                                  
    * Input Buffer 214 bytes -                                                                                      
    *               begin transaction    insert into DocContabile   select *  f                                     
    *  rom gunoiDocContabile      rollback                                                                          
    *  MODULE                          BASE      END       SIZE                                                     
    * sqlservr                       0000000000690000  00000000042A1FFF  03c12000                                   
    * ntdll                          0000000077730000  00000000778D8FFF  001a9000                                   
    * kernel32                       0000000077510000  000000007762EFFF  0011f000                                   
    * KERNELBASE                     000007FEFD6E0000  000007FEFD74AFFF  0006b000                                   
    * ADVAPI32                       000007FEFE090000  000007FEFE16AFFF  000db000                                   
    * msvcrt                         000007FEFE300000  000007FEFE39EFFF  0009f000                                   
    * sechost                        000007FEFF590000  000007FEFF5AEFFF  0001f000                                   
    * RPCRT4                         000007FEFF5B0000  000007FEFF6DCFFF  0012d000                                   
    * MSVCR80                        0000000071710000  00000000717D8FFF  000c9000                                   
    * MSVCP80                        0000000071600000  0000000071708FFF  00109000                                   
    * sqlos                          00000000715F0000  00000000715F6FFF  00007000                                   
    * Secur32                        000007FEFD1E0000  000007FEFD1EAFFF  0000b000                                   
    * SSPICLI                        000007FEFD3B0000  000007FEFD3D4FFF  00025000                                   
    * pdh                            000007FEF90C0000  000007FEF910DFFF  0004e000                                   
    * SHLWAPI                        000007FEFDE50000  000007FEFDEC0FFF  00071000                                   
    * GDI32                          000007FEFE3A0000  000007FEFE406FFF  00067000                                   
    * USER32                         0000000077630000  0000000077729FFF  000fa000                                   
    * LPK                            000007FEFDE40000  000007FEFDE4DFFF  0000e000                                   
    * USP10                          000007FEFF970000  000007FEFFA38FFF  000c9000                                   
    * USERENV                        000007FEFC850000  000007FEFC86DFFF  0001e000                                   
    * profapi                        000007FEFD510000  000007FEFD51EFFF  0000f000                                   
    * WINMM                          000007FEFB320000  000007FEFB35AFFF  0003b000                                   
    * IPHLPAPI                       000007FEFAD70000  000007FEFAD96FFF  00027000                                   
    * NSI                            000007FEFDFB0000  000007FEFDFB7FFF  00008000                                   
    * WINNSI                         000007FEFAD60000  000007FEFAD6AFFF  0000b000                                   
    * opends60                       0000000071590000  0000000071597FFF  00008000                                   
    * NETAPI32                       000007FEFAEB0000  000007FEFAEC5FFF  00016000                                   
    * netutils                       000007FEFAEA0000  000007FEFAEABFFF  0000c000                                   
    * srvcli                         000007FEFD060000  000007FEFD082FFF  00023000                                   
    * wkscli                         000007FEFAE80000  000007FEFAE94FFF  00015000                                   
    * LOGONCLI                       000007FEFCB90000  000007FEFCBBFFFF  00030000                                   
    * SAMCLI                         000007FEFAE60000  000007FEFAE73FFF  00014000                                   
    * BatchParser                    0000000071560000  000000007158CFFF  0002d000                                   
    * IMM32                          000007FEFE060000  000007FEFE08DFFF  0002e000                                   
    * MSCTF                          000007FEFE1F0000  000007FEFE2F8FFF  00109000                                   
    * psapi                          00000000778F0000  00000000778F6FFF  00007000                                   
    * instapi10                      0000000071320000  000000007132CFFF  0000d000                                   
    * cscapi                         000007FEF7FA0000  000007FEF7FAEFFF  0000f000                                   
    * sqlevn70                       0000000071100000  0000000071303FFF  00204000                                   
    * CRYPTSP                        000007FEFCE50000  000007FEFCE66FFF  00017000                                   
    * rsaenh                         000007FEFCA70000  000007FEFCAB6FFF  00047000                                   
    * CRYPTBASE                      000007FEFD440000  000007FEFD44EFFF  0000f000                                   
    * BROWCLI                        000007FEF8B80000  000007FEF8B91FFF  00012000                                   
    * AUTHZ                          000007FEFCF70000  000007FEFCF9EFFF  0002f000                                   
    * MSCOREE                        000007FEF8980000  000007FEF89EEFFF  0006f000                                   
    * ole32                          000007FEFDC30000  000007FEFDE32FFF  00203000                                   
    * credssp                        000007FEFC960000  000007FEFC969FFF  0000a000                                   
    * msv1_0                         000007FEFCD90000  000007FEFCDE0FFF  00051000                                   
    * cryptdll                       000007FEFD090000  000007FEFD0A3FFF  00014000                                   
    * kerberos                       000007FEFCCD0000  000007FEFCD83FFF  000b4000                                   
    * MSASN1                         000007FEFD5B0000  000007FEFD5BEFFF  0000f000                                   
    * schannel                       000007FEFCB00000  000007FEFCB55FFF  00056000                                   
    * CRYPT32                        000007FEFD7D0000  000007FEFD939FFF  0016a000                                   
    * security                       0000000071390000  0000000071392FFF  00003000                                   
    * WS2_32                         000007FEFF360000  000007FEFF3ACFFF  0004d000                                   
    * SHELL32                        000007FEFE5D0000  000007FEFF357FFF  00d88000                                   
    * OLEAUT32                       000007FEFDED0000  000007FEFDFA6FFF  000d7000                                   
    * ncrypt                         000007FEFCF20000  000007FEFCF6CFFF  0004d000                                   
    * bcrypt                         000007FEFCEF0000  000007FEFCF11FFF  00022000                                   
    * mswsock                        000007FEFCDF0000  000007FEFCE44FFF  00055000                                   
    * wship6                         000007FEFCFB0000  000007FEFCFB6FFF  00007000                                   
    * wshtcpip                       000007FEFC720000  000007FEFC726FFF  00007000                                   
    * ntmarta                        000007FEFC620000  000007FEFC64CFFF  0002d000                                   
    * WLDAP32                        000007FEFE410000  000007FEFE461FFF  00052000                                   
    * ntdsapi                        000007FEF7AF0000  000007FEF7B16FFF  00027000                                   
    * bcryptprimitives               000007FEFC9D0000  000007FEFCA1BFFF  0004c000                                   
    * SAMLIB                         000007FEFBE10000  000007FEFBE2CFFF  0001d000                                   
    * CLBCatQ                        000007FEFD960000  000007FEFD9F8FFF  00099000                                   
    * sqlncli10                      0000000063720000  00000000639DCFFF  002bd000                                   
    * VERSION                        000007FEFC650000  000007FEFC65BFFF  0000c000                                   
    * COMCTL32                       000007FEFA110000  000007FEFA1AFFFF  000a0000                                   
    * COMDLG32                       000007FEFDFC0000  000007FEFE056FFF  00097000                                   
    * SQLNCLIR10                     00000000636E0000  0000000063716FFF  00037000                                   
    * netbios                        000007FEF4340000  000007FEF4349FFF  0000a000                                   
    * xpstar                         0000000063650000  00000000636D7FFF  00088000                                   
    * SQLSCM                         0000000063640000  000000006364DFFF  0000e000                                   
    * ODBC32                         000007FEF0AC0000  000007FEF0B70FFF  000b1000                                   
    * ATL80                          0000000063620000  000000006363FFFF  00020000                                   
    * odbcint                        00000000635E0000  0000000063617FFF  00038000                                   
    * clusapi                        000007FEF91B0000  000007FEF91FFFFF  00050000                                   
    * resutils                       000007FEF9190000  000007FEF91A8FFF  00019000                                   
    * xpstar                         00000000635B0000  00000000635D4FFF  00025000                                   
    * dbghelp                        0000000063330000  000000006348DFFF  0015e000                                   
    *     P1Home: 000000000BB6A950:  00000000C0000005  0000000000000000  0000000000886B00  0000000000000002  00000000
    What else should I have to do?
    Thank you,
    Horia

  • Can't save BISM file pointing to excel sheet (data source). ErrMsg: "There were errors found while validating the page: Cannot connect to the server or database."

    Hi,
    Me and a collegue is administrering our new enterprise BI portal in SharePoint 2013 (On Premise) and have a problem with using a specific Excel file including general ledger data as data source through a BISM file.
    This particular BISM file can't be saved without getting the error message "There were errors found while validating the page: Cannot connect to the server or database."
    BISM files against other Excel sheets and sources (for example SSAS tabular databases) works well.
    Can anyone help us pinpointing whats wrong here, this is a really important stakeholder in our organization requesting this reporting?
    Cheers!

    Hi E.SWARD ,
    My self created a Power pivot excel then i want to use this excel to create BI file . Still i am getting the same error . Pls help me to resolve this issue
    Cannot connect to the server or database.
    I am getting the similar error , if i use Tabular analysis server instance .
    Subhash

  • An error has occurred while accessing SQL database or system resources. If this is the first time you have seen this message, please try again later. If this problem persists, please contact your administrator.

    I have SP Server 2010, and when I try to DELETE a rule within an existing Audience, "Property (Account Name) = domain/username", I get this error, "An error has occurred while accessing SQL database or system resources. If this
    is the first time you have seen this message, please try again later. If this
    problem persists, please contact your administrator."  When I try to "MODIFY" the rule I get this error, "One or more values typed on this page are not valid. Check the text for the indicated fields." 
    The last time I checked it was working, I'm not aware of any new updates installed recently?  I did a full Profile Synchronization as well, but still not working, please advise? -- Evenstarline

    Hi Sara,
    First of all thank you very much for your prompt responses. Here are my comments to each of your suggestions below, and just to let you know I am using a Farm Admin account.  I
    was able to do this way after we upgraded from SP 2007 to SP 2010 as well.   I would like to mention I'm not a SP expert, just been given the responsibility due to another person handling it just left, so apologize with some of
    my novice questions below?
    1. When I change the Operators to "Contains" or "Not Contains" get generates this error below.
         Error generating in red towards top of the audience page..."One or more values typed on this page are not valid.  Check the text for the indicated fields."
         Error occurred where you enter your "Value"..."Could not resolve the user identity. Please re-enter the account name."
    2. We have a 3-server-tier topology (SPWeb, SPDB, and SPFarm).  Does the updates only apply to where the Central Admin is installed, which is the "SPFarm"?  I checked all
    3 servers, and NONE of the updates (KB2899494, KB2889845, and KB2883055) you'd mentioned are installed.
    3. I'm new to IISRET, I need to be extra cautious of what I run in production, is this safe to run with no problem?  What does it do?  And How do I run it?
    4. I'm also new to viewing the ULS log.  I'd just downloaded a viewer for it.  I'm assuming the only logs I need to be concern with viewing are within the SPAdmin (where Central
    Admin is installed)?  There's so many of them, what should I be looking for exactly?
    Evenstarline 

  • In "purchases" while in my App Store, Mountain Lion says, "an error has occurred" and the green 'download' button is grey and I cannot re-start the download. I was abroad when I purchased this app and during download, my internet connection was lost.

    In "purchases" while in my App Store, Mountain Lion says, "an error has occurred" and the green 'download' button is grey and I cannot re-start the download. I was abroad when I purchased this app and during download, my internet connection was lost. At the time, Apple was still offering the e-chat, so I did that and the man was very helpful and it was a quick fix, so my download button turned green again, and I was able to begin the download. BUT during the download, I was kicked offline once again, and I decided to wait until I was back in the USA. I will go in to an Apple store and ask assistance, but if there is something I am missing, I'd like to try that first. Thanks in advance for any advice.

    Welcome to the support forums.
    Please ask this question in the Mac App Store forum where they can better assist you.

Maybe you are looking for