Database error ZMM 3.0

Hi,
I'm having some problems with ZENworks Mobile Management 3.0 which I can't figure out.
Some info:
MS Server 2008 R2
SQL Server 2008 SP1
All updates installed
I have a functional LDAP connection to our AD.
When I'm registering new devices through the ZENworks application on iOS-devices everything works like a charm and the APN profile is installed without any problems.
So far so good, I can now make changes to our default policy and the changes are applied to the device.
Now to the juicy part, when I create iOS Corporate Resources and choose to deploy to an LDAP group (which I'm a member of) I can see in the dashboard that the resource is delivered to my user and device.
But the resource is never deployed to the physical device. Then I looked in the logs on the device and found these two errors in the iOS MDM Sync Log:
Error
CIOSMDMCommandBase::CheckStatus
Device returned ERROR status
Database Error
ExecuteSQL
Failed running query:
DELETE FROM CommandsByDevice WHERE DeviceSAKey = ? AND UUID = ?
SQLError:
ExecuteSQL returned status: -1
State: 23000
Native: 547
Error: [Microsoft][ODBC SQL Server Driver][SQL Server]The DELETE statement conflicted with the REFERENCE constraint ""FK_Profile_For_Removal"".
The conflict occurred in database ""MDM"", table ""dbo.iOSProfilesForRemoval"", column 'CommandsByDeviceSAKey'
When I get this error the device stops talking to the MDM and no changes are applied to it. I have tried on different devices and with other LDAP-accounts but same error is presenting itself.
The only way to get rid of this is by resetting the device for enrollment, then everything works until I assign a iOS Corporate Resource.
I can assign a iOS Corporate Resource directly to the user and that works just fine.
Ideas?
Thanks,
Rasmus

I am not seeing exactly the same thing as what you are describing. I have had issues with deploying Apps, including Managed Apps. I do notice that several of the teachers that I support recently updated to iOS 8 which caused some working profiles to fail. Once I removed and reloaded the configuration I noticed that the profiles only had the single MDM listed. Everything acted like it was working so I haven't looked at it further. I don't personally have iOS 7 devices so can't check tonight but will look to see if any of my other iPads I support show only a single profile setup. My iOS 8 iPhone (4s) only has the single profile with listed items under that profile so I am guessing that is how Apple is now handling things.
Richard

Similar Messages

In SM21 - Database error 235 at EXE

Hello Gurus,
In sm21 - Database error 235 at EXE this error shown in our test server, while investigating I found this
( I am attaching log for your reference )
Details
Recording at local and central time........................ 25.03.2009 23:02:24
Task................ 15116 / Background Processor No. 18
User................ CSCADMIN_BC
Client.............. 050
Terminal............
Session............. 1
Transaction code....
Program name........ RSORAHST
Problem class....... K    SAP Web AS Problem
Development class... SBAC
Module name......... dbds
Line................ 798
Table name.......... 235
Field name.......... EXE
Documentation for system log message BY 2 :
After the attempt to call a database operation, the database system has
returned the error code specified in the message, which indicates that
the operation concerned could not be executed successfully.
Technical details
File................ 018863
Position............ 0000235620
Entry type.......... h      ( Database Error (Non-SQL)       )
Message ID.......... BY 2
Variable parts...... 235       EXE                                       dbds    798
The given program associated with this job SAP_PERIODIC_ORACLE_SNAPSHOT but this is run successfully on the test server.
Can somebody tell me the error & the rectification for the same
Thanks & regards
Shishir

Please check
- ST22 for dumps
- alert<SID>.log of the database
- dev_w18 tracefile
Do you use the same patches on both DEV and this system?
Markus

Business rule in MDS 2012 error: A database error has occurred. Contact your system administrator.

I get the following information in my MDS log as well as the above error message when I execute a business rule that has a condition of AND and an Action of Attribute must be unique in combination with 2 other attributes.
I'm running SQL Server 2012 11.0.3000
MDS database version 11.1.0.0
Any ideas?
MDS Error: 0 : SqlException message: A database error has occurred. Contact your system administrator.
at Microsoft.MasterDataServices.Core.DataAccess.DbHelper.HandleExceptions(Exception ex)
at Microsoft.MasterDataServices.Core.DataAccess.DbHelper.ExecuteDataSet(String spName, CloseConnectionBehavior closeBehavior, Object[] parameterValues)
at Microsoft.MasterDataServices.Core.DataAccess.MasterDataAccess.<>c__DisplayClass5.<ValidateEntityMembers>b__4()
at Microsoft.MasterDataServices.Core.DataAccess.DbHelper.ExecuteMethodWithDeadlockProtection(MethodDelegate method)
at Microsoft.MasterDataServices.Core.BusinessLogic.Validations.ValidateMembers(Int32 versionId, Identifier entityIdentifier, IList`1 memberIds, RequestContext context, OperationResult results)
at Microsoft.MasterDataServices.Core.BusinessLogic.Validations.Process(ValidationProcessCriteria criteria, Boolean commitVersion, Boolean validateEntityAsync, Boolean returnValidationResults, RequestContext context, OperationResult results)
SQL Error Debug Info: Number: 208, Message: Invalid object name 'cteDuplicates0a070e37b106b9e3efe35a455076efa7'., Server: SQLRS-01, Proc: udp_SYSTEM_3_38_CHILDATTRIBUTES_ProcessRules, Line: 230
SQL Error Debug Info: Number: 266, Message: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1., Server: SQLRS-01, Proc: udp_SYSTEM_3_38_CHILDATTRIBUTES_ProcessRules, Line: 230
SQL Error Debug Info: Number: 266, Message: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1., Server: SQLRS-01, Proc: , Line: 0
SQL Error Debug Info: Number: 266, Message: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1., Server: SQLRS-01, Proc: udpBusinessRule_AttributeMemberController, Line: 0
SQL Error Debug Info: Number: 266, Message: Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1., Server: SQLRS-01, Proc: udpValidateMembers, Line: 0
DateTime=2013-08-15T13:25:15.6684023Z
MDS Error: 0 : <ArrayOfError xmlns="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
<Error>
<Code>208</Code>
<Context i:nil="true" />
<Description>A database error has occurred. Contact your system administrator.</Description>
</Error>
</ArrayOfError>
DateTime=2013-08-15T13:25:15.7152026Z

OK I bit the bullet and contacted support on this one.
There is a known issue with MDS 2012 and business rules with a combination of "must be unique" attributes. If you do not list the attributes in the same order that they were created you will get the generic error I cited. At first they told me it must be
in the same order the attributes are in and that worked on one entity but not the other. The difference was that in the second entity I previously rearranged the attributes in question. Once I changed the order in the business rule to reflect the *original*
order it worked like a champ.
Hopefully this helps save someone some time and money.

BO 4.0 - Database error: Unable to connect to SAP BW Incomplete logon data

Hello Experts,
I have enabled a 'SSO to database' between SAP BW and Business objects by referencing to the documents related to below link.
[http://wiki.sdn.sap.com/wiki/display/BOBJ/HowtosetupSSOagainstSAPBWinSBOBI4.0forLDAPusers]
I have created a universe connection with option 'use single sign on when refreshing reports at view time' and have created a universe on top of my BEx query by log-in to the universe designer tools using my LDAP account.
Now when I run the report with either SAP account or LDAP - I am able to run a adhoc webi report on this universe and get data either through the webi rich client or via BO 4.0 Info-view/Launch Pad.
But the issue is that when other users are trying to run webi queries on this universe either through Info-view/launch pad or rich client by log-in via LDAP Authentication - they get the below error: I have given SAP_ALL to this user for time being and also have done the necessary configuration for 'simple user format' in CMC so these user has 1 account with 3 alias definitions: Enterprise, SAP, R/3.
Database error: Unable to connect to SAP BW server Incomplete logon data -
If the user logs on into the BO 4.0 Info-view/launch pad or webi rich client using his SAP authentication than he is able to run and retrieve data.
I also get a dump in the SAP BW system - I analyzed the dump in SAP BW using st22 tcode and it gives the error short text as - Incomplete logon data and run-time error - CALL_FUNCTION_SIGNON_INCOMPL
Desired outcome:
I want the users to log-in to webi rich client or BO 4.0 Launch pad/Info-view using their 'LDAP' authentication and run reports against the universe on SAP BW/BEx query without any errors or additional username/password requirements.
Can someone please tell me if I am missing any steps/configuration and guide me to achieve the above mentioned desired result ?
Any help in this matter would be greatly appreciated.
Thanks & regards,
CD.

Hi Simone,
Thank you for the reply.
Here are the things done by me.
1. Generated the keystore file and imported it in BI 4.0 CMC on SAP Authentication Option tab
    ([http://wiki.sdn.sap.com/wiki/display/BOBJ/GeneratekeystoreandcertificateforSAPBO+BI4.0])
    ([http://wiki.sdn.sap.com/wiki/display/BOBJ/SetupofSAPSSOServiceinSAPBOBI4.0+CMC])
2. Generate the certificate file cert.der and this cert is imported in SAP BW with STRUSTSSO2 transaction.
    ([http://wiki.sdn.sap.com/wiki/display/BOBJ/ImportSAPBOBI4.0certificateintoSAP+BW])
3. BW Roles/Users have been imported into CMC.
4. SAP Users and LDAP users are mapped/aliased with each other using the registry key method
    ([http://wiki.sdn.sap.com/wiki/display/BOBJ/HowtomapSAPusersandLDAPusersinSBOBI4.0+CMC])
I haven't explicitly configured STS (Security token service) as STS is a part of Adaptive processing server (APS) and I have verified that by going to servers in CMC and then to analysis services.
I have searched for SAP OSS notes related to my issue but couldn't find any note related to SAP BW SSO with Business objects 4.0. Most of the notes are relevant for BO XI 3.1 environments.
Thanks & regards,
CD.

BO 4.0: Database error:Unable to connect to SAP BW server Incomplete logon

Hello Experts,
I have enabled a 'SSO to database' between SAP BW and Business objects by referencing to the documents related to below link.
http://wiki.sdn.sap.com/wiki/display/BOBJ/HowtosetupSSOagainstSAPBWinSBOBI4.0forLDAPusers
I have created a universe connection with option 'use single sign on when refreshing reports at view time' and have created a universe on top of my BEx query by log-in to the universe designer tools using my LDAP account.
Now when I run the report with either SAP account or LDAP - I am able to run a adhoc webi report on this universe and get data either through the webi rich client or via BO 4.0 Info-view/Launch Pad.
But the issue is that when other users are trying to run webi queries on this universe either through Info-view/launch pad or rich client by log-in via LDAP Authentication - they get the below error: I have given SAP_ALL to this user for time being and also have done the necessary configuration for 'simple user format' in CMC so these user has 1 account with 3 alias definitions: Enterprise, SAP, R/3.
Database error: Unable to connect to SAP BW server Incomplete logon data -
If the user logs on into the BO 4.0 Info-view/launch pad or webi rich client using his SAP authentication than he is able to run and retrieve data.
I also get a dump in the SAP BW system - I analyzed the dump in SAP BW using st22 tcode and it gives the error short text as - Incomplete logon data and run-time error - CALL_FUNCTION_SIGNON_INCOMPL
Desired outcome:
I want the users to log-in to webi rich client or BO 4.0 Launch pad/Info-view using their 'LDAP' authentication and run reports against the universe on SAP BW/BEx query without any errors or additional username/password requirements.
Can someone please tell me if I am missing any steps/configuration and guide me to achieve the above mentioned desired result ?
Any help in this matter would be greatly appreciated.
Thanks & regards,
CD.

Whether your problem is solved?
We have the same problem in BO Mobile.
Two users from one BW-role, BO-groups; one user report is executed, another user - error incomplete logon data. In Web Intelligence both users reports succeeds.

Getting database error while updating data to mysql table.

user registration.jsp < jsp user view to get input >
<?xml version="1.0" encoding ="UTF-8"?>
<%@ taglib prefix="c"   uri="http://java.sun.com/jsp/jstl/core" %>
<%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
<%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %>
<%@ taglib prefix="x"   uri="http://java.sun.com/jsp/jstl/xml" %>
<%@ taglib prefix="fn" uri="http://java.sun.com/jsp/jstl/functions" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Registeres USers Login Page</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<body>
<%--debugging code--%>
<%@ include file="debug.jsp" %>
<table width="1049" cellpadding="5" align="center">
<tr>
    <td width="2378"><div align="center">
      <h2 align="center"> User Registration</h2>
       <p>
     <c:url var="HmePgeURL" value="/cw/router/home" scope="page"/>
     <a href="${HmePgeURL}">Home</a>  <c:url var='BSPgeURL' value='/cw/router/login' scope='page'/>
     <a href="${BSPgeURL}">Buy or Sell</a>
     </p>
    </div></td>
</tr>
</table>
<p align="center"> </p>
<p>This website is only open to members of the De MontFort University.
You will need a current @learner.dmu.ac.uk e-mail address in order to register.</p>
<p> If you've already registered for one site you do not need to register again </p>
<c:url value="/cw/router/userregistration" var="UregPgeURL" scope="page"/>
<form name="frmregister" method="post" action="${UregPgeURL}">
<div>
<table width="726" height="285" border="0" align="left" cellpadding="2" cellspacing="0">
    <tr>
      <td width="157" align="right" >Name:</td>
      <td width="561" > <input name="txtname" type="text" value="${param.txtname}"/> </td>
    </tr>
      <c:if test="${!empty requestScope.reqInvalidUserName}">
      <c:out value="${requestScope.reqInvalidUserName}"/>
      </c:if>
    <tr>
      <td width="157" align="right" >Department</td>
      <td align="left" >
          <select name="txtdepartment" value="${param.txtdepartment}" >
            <option></option>
            <option value="Faculty of Art and Design">Faculty of Art and Design</option>
            <option value="Faculty of Business and Law">Faculty of Business and Law</option>
            <option value="Faculty of Computing Sciences and Engineering">Faculty of Computing Sciences and Engineering</option>
            <option value="Faculty of Health and Life Sciences">Faculty of Health and Life Sciences</option>
            <option value="Faculty of Humanities">Faculty of Humanities</option>
          </select>
      </td>
    </tr>
      <tr>
        <td align="right" >Programme</td>
        <td ><input type="text" name="txtprogramme" value="${param.txtprogramme}" />
          (eg: BIS,SE) </td>
      </tr>
      <tr>
      <td align="right" >Telephone Number: </td>
      <td ><input name="txtphonenum" type="text" value="${param.txtphonenum}" /></td>
    </tr>
    <tr>
      <td align="right" >Date Of Birth: </td>
      <td ><input name="txtday" type="text" size="15" value="${param.txtdob}" />(of format YYYY-MM-DD)</td>
      </tr>
    <tr>
      <td align="right" >Username</td>
      <td align="left" >
          <input name="txtuserid" type="text" size="15" value="${param.txtuserid}" />
        (eg. p07269027 from [email protected])</td>
        <c:if test="${!empty requestScope.reqInvalidUserId}">
        <c:out value="${requestScope.reqInvalidUserId}"/>
        </c:if>
    </tr>
    <tr>
      <td align="right" >Password</td>
      <td align="left" >
          <input name="txtpassword" type="password" size="15" value="${param.txtpassword}" />
      </td></tr>
     <c:if test="${!empty requestScope.reqInvalidPassword}">
      <c:out value="${requestScope.reqInvalidPassword}"/>
      </c:if>
    <tr>
      <td align="right" >Confirm Password </td>
      <td align="left" >
          <input name="txtpasswordconf" type="password" size="15" />
      </td>
    </tr>
    <tr>
      <td colspan="2" align="center">
        <input name="frmsubmit" type="submit" value="Register User" />
        <input type="reset" name="Reset" value="Reset" />
      </td>
    </tr>
</table>
     <c:if test="${!empty requestScope.reqQueryErrorMessage}">
      <c:out value="${requestScope.reqQueryErrorMessage}"/>
      </c:if>
     <c:if test="${!empty requestScope.reqInvalidUpdate}">
      <c:out value="${requestScope.reqInvalidUpdate}"/>
      </c:if>
</div>
</form>
</body>
</html>
proregistration.jsp ( registration process jsp)
<?xml version="1.0" encoding ="UTF-8"?>
<%@ taglib prefix="c"   uri="http://java.sun.com/jsp/jstl/core" %>
<%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
<%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %>
<%@ taglib prefix="x"   uri="http://java.sun.com/jsp/jstl/xml" %>
<%@ taglib prefix="fn" uri="http://java.sun.com/jsp/jstl/functions" %>
<%-- \WEB-INF\jsp\cwjsps\probooksforsale.jsp --%>
<%-- Probookforsale --%>
<%-- skip field validation and provide blankpage if first time in --%>
<c:if test="${empty param.frmsubmit}">
<c:set var="reqOutcome" scope="request" value=" "/>
<jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/> <%-- initial request --%>
</c:if>
<%-- validate txtname --%>
<c:if test="${empty param.txtname}">
<c:set var="reqInvalidUserName" scope="request" value= "User Name Cannot Be Empty"/>
</c:if>
<%-- validate txtuserid --%>
<c:if test="${empty param.txtuserid}">
<c:set var="reqInvalidUserId" scope="request" value= "User ID Cannot Be Empty"/>
</c:if>
<%-- validate txtpassword--%>
<c:if test="${empty param.txtpassword}">
<c:set var="reqInvalidPassword" scope="request" value= "Password Cannot Be Empty"/>
</c:if>
<%-- if userid invalid or username invalid --%>
<%-- redisplay form with originl typed-in data and with errors marked --%>
<c:if test="${empty param.txtname or empty param.txtuserid}">
<c:set var="reqOutcome" scope="request" value= "failure" />
<jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/> <%-- failure --%>
</c:if>
<c:catch var="pgeQueryError">
<sql:update var="pgeRowCount" scope="page" >
<%-- insert details to trader table --%>
INSERT INTO trader(dbTraderName,dbTraderDepartment,dbTraderProgramme,dbTraderPhoneNum ,dbTraderDOB,dbTraderPNumber,dbTraderPwd)
VALUES(?,?,?,?,?,?,?)
<sql:param value="${param.txtname}"/>
<sql:param value="${param.txtdepartment}"/>
<sql:param value="${param.txtprogramme}"/>
<sql:param value="${param.txtphonenum}"/>
<sql:param value="${param.txtdob}"/>
<sql:param value="${param.txtuserid}"/>
<sql:param value="${param.txtpassword}"/>
</sql:update>
</c:catch>
<%-- check For query Error --%>
<c:if test="${not empty pgeQueryError}">
<c:choose>
<%-- check duplicate record --%>
<c:when test="${pgeQueryError.rootCause.errorCode =='1062'}">
<c:set var="reqQueryErrorMessage" scope="request" value="User already Registered - Duplicate Record" />
<jsp:forward page="/WEB-INF/jsp/cwjsps/login.jsp"/>
</c:when>
<c:otherwise>
<%-- database error --%>
<c:set var="reqQueryErrorMessage" scope="request" value="Database Error" />
<jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/>
</c:otherwise>
</c:choose>
<c:set var="reqOutcome" scope="request" value="failure" />
<jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/>
</c:if>
<%-- check For no rows returned --%>
<c:if test="${pgeRowCount !=1}">
<c:set var="reqInvalidUpdate" scope="request" value="*** rowCount not = 1"/>
<c:set var="reqOutcome" scope="request" value="failure"/>
<jsp:forward page="/WEB-INF/jsp/cwjsps/userregistration.jsp"/> <%-- failure --%>
</c:if>
<%-- Otherwise --%>
<%-- Outcome is success --%>
<c:if test="${pgeRowCount ==1}">
<c:set var="reqOutcome" scope="request" value="success" />
<jsp:forward page="/WEB-INF/jsp/cwjsps/login.jsp"/> <%-- success --%>
</c:if>
router.jsp ( maps the jsp page based on success and failure)
<?xml version="1.0" encoding ="iso-8859-1"?>
<%-- /WEB-INF/jsp/cwjsps/router.jsp --%>
<%@ taglib prefix="c"   uri="http://java.sun.com/jsp/jstl/core" %>
<%@ taglib prefix="fmt" uri="http://java.sun.com/jsp/jstl/fmt" %>
<%@ taglib prefix="sql" uri="http://java.sun.com/jsp/jstl/sql" %>
<%@ taglib prefix="x"   uri="http://java.sun.com/jsp/jstl/xml" %>
<%@ taglib prefix="fn" uri="http://java.sun.com/jsp/jstl/functions" %>
<%-- setup session if one does not exist --%>
<%@ page session="true" %>
<%-- set up debug variable --%>
<c:set var="sessDebug" scope="session" value="true"/>
<%-- get pathinfo information from the request --%>
<%-- this defines which use case has been requested --%>
<c:set var="pgePathInfo" scope="page" value="${pageContext.request.pathInfo}" />
<%-- uc02 : Login --%>
<c:if test="${pageScope.pgePathInfo =='/home'}" >
<jsp:forward page="/WEB-INF/jsp/cwjsps/home.jsp"/>
</c:if>
<c:if test="${pageScope.pgePathInfo =='/login'}" >
<jsp:forward page="/WEB-INF/jsp/cwjsps/prologin.jsp"/>
</c:if>
<%-- uc01 : View Details Of Books For Sale --%>
<c:if test="${pageScope.pgePathInfo =='/viewbooksforsale'}" >
<jsp:forward page="/WEB-INF/jsp/cwjsps/probooksforsale.jsp"/>
</c:if>
<%-- uc01 : process User registration--%>
<c:if test="${pageScope.pgePathInfo =='/userregistration'}" >
<jsp:forward page="/WEB-INF/jsp/cwjsps/proregistration.jsp"/>
</c:if>
<%-- uc01 : debug --%>
<c:if test="${pageScope.pgePathInfo =='/debug'}" >
<jsp:forward page="/WEB-INF/jsp/cwjsps/debug.jsp"/>
</c:if>
<%-- uc01 : view Traders Own View --%>
<c:if test="${pageScope.pgePathInfo =='/Traderhomepage'}" >
<jsp:forward page="/WEB-INF/jsp/cwjsps/Traderhomepage.jsp"/>
</c:if>
<%-- otherwise --%>
<jsp:forward page="/WEB-INF/jsp/cwjsps/home.jsp"/>                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          &nb

Hi..
Correcting the record from PSA is temporary solution depends on u r criticality....
Only Solution is to correct the record at source system level... Generally Material master data record is imp so just try to fix temporarily so that it vl not affect u r loads until it is corrected at Source System level..
Note: inform the problem to u r co-ordinator and try to correct it ASAP... and explain the temp solution(PSA correction)...
cheers..

Akonadi database error code: 1062 Duplicate entry for key

Since my email provider migrated their webmail platform, I keep getting an error each time kmail attempts to get emails from their imap server: could not create collection INBOX resourceid: 17
I double checked the provided imap settings have not changed and are correct : imap.laposte.net port 993 using SSL/TLS
As you can see in the pasted akonadi self-test report below, I have a few errors related to innodb, the absence of mysql tables in local/share/akonadi/db_data/ and the table performance_schema having the wrong structure. Those have been there for several months but I've been unable to fix them and I didn't care because my email was working. I suppose they are unrelated to my current issues.
Any help I can get is much welcome.
Akonadi Server Self-Test Report
===============================
Test 1: SUCCESS
Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system.
File content of '/home/the_user/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-the_user.kKTLSR/mysql.socket"
ServerPath=/usr/bin/mysqld
StartServer=true
User=
Password=
[Debug]
Tracer=null
[QPSQL]
StartServer=true
Name=akonadi
Host=
User=
Password=
Port=5432
[SQLITE]
Name=akonadi
Test 2: SUCCESS
Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.
Test 3: SUCCESS
MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server '/usr/bin/mysqld'.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution.
Test 4: SUCCESS
MySQL server is executable.
Details: MySQL server found: /usr/bin/mysqld Ver 10.0.14-MariaDB-log for Linux on x86_64 (MariaDB Server)
Test 5: ERROR
MySQL server log contains errors.
Details: The MySQL server error log file '<a href='/home/the_user/.local/share/akonadi/db_data/mysql.err'>/home/the_user/.local/share/akonadi/db_data/mysql.err</a>' contains errors.
File content of '/home/the_user/.local/share/akonadi/db_data/mysql.err':
141129 9:34:33 [Warning] You need to use --log-bin to make --binlog-format work.
2014-11-29 09:34:33 7f5b81d0b780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
141129 9:34:33 [Note] InnoDB: Using mutexes to ref count buffer pool pages
141129 9:34:33 [Note] InnoDB: The InnoDB memory heap is disabled
141129 9:34:33 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
141129 9:34:33 [Note] InnoDB: Memory barrier is not used
141129 9:34:33 [Note] InnoDB: Compressed tables use zlib 1.2.8
141129 9:34:33 [Note] InnoDB: Using Linux native AIO
141129 9:34:33 [Note] InnoDB: Using CPU crc32 instructions
141129 9:34:33 [Note] InnoDB: Initializing buffer pool, size = 80.0M
141129 9:34:33 [Note] InnoDB: Completed initialization of buffer pool
141129 9:34:33 [Note] InnoDB: Highest supported file format is Barracuda.
141129 9:34:33 [Note] InnoDB: The log sequence numbers 66340678877 and 66340678877 in ibdata files do not match the log sequence number 66344113222 in the ib_logfiles!
141129 9:34:33 [Note] InnoDB: Database was not shutdown normally!
141129 9:34:33 [Note] InnoDB: Starting crash recovery.
141129 9:34:33 [Note] InnoDB: Reading tablespace information from the .ibd files...
141129 9:34:33 [Note] InnoDB: Restoring possible half-written data pages
141129 9:34:33 [Note] InnoDB: from the doublewrite buffer...
141129 9:34:34 [Note] InnoDB: 128 rollback segment(s) are active.
141129 9:34:34 [Note] InnoDB: Waiting for purge to start
141129 9:34:34 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.20-68.0 started; log sequence number 66344113222
141129 9:34:34 [Note] Plugin 'FEEDBACK' is disabled.
141129 9:34:34 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist
141129 9:34:34 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
141129 9:34:34 [ERROR] Native table 'performance_schema'.'cond_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_history_long' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_host_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_instance' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_thread_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_user_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_by_account_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_waits_summary_global_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_summary_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'file_summary_by_instance' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'host_cache' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'mutex_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'objects_summary_global_by_type' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'performance_timers' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'rwlock_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_actors' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_consumers' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_instruments' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_objects' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'setup_timers' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_index_usage' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_io_waits_summary_by_table' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'table_lock_waits_summary_by_table' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'threads' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_current' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_history' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_history_long' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_thread_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_account_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_user_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_by_host_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_stages_summary_global_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_current' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_history' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_history_long' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_thread_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_account_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_user_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_host_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_global_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'events_statements_summary_by_digest' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'users' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'accounts' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'hosts' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_instances' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_summary_by_instance' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'socket_summary_by_event_name' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'session_connect_attrs' has the wrong structure
141129 9:34:34 [ERROR] Native table 'performance_schema'.'session_account_connect_attrs' has the wrong structure
141129 9:34:34 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1146: Table 'mysql.gtid_slave_pos' doesn't exist
141129 9:34:34 [Note] Reading of all Master_info entries succeded
141129 9:34:34 [Note] Added new Master_info '' to hash table
141129 9:34:34 [Note] /usr/bin/mysqld: ready for connections.
Version: '10.0.14-MariaDB' socket: '/tmp/akonadi-the_user.kKTLSR/mysql.socket' port: 0 MariaDB Server
2014-11-29 09:34:34 7f5b81c77700 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
141129 15:14:56 [Warning] Aborted connection 58 to db: 'akonadi' user: 'the_user' host: '' (Unknown error)
Test 6: SUCCESS
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href='/usr/share/config/akonadi/mysql-global.conf'>/usr/share/config/akonadi/mysql-global.conf</a>.
File content of '/usr/share/config/akonadi/mysql-global.conf':
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
# Based on advice by Kris KÃ¶hntopp <[email protected]>
[mysqld]
# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables
# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
#expire_logs_days=3
#sync_bin_log=0
# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M
# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M
# Create a .ibd file for each table (default:0)
innodb_file_per_table=1
# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2
# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M
# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M
# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err
# print warnings and connection errors (default:1)
log_warnings=2
# Convert table named to lowercase
lower_case_table_names=1
# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M
# Maximum simultaneous connections allowed (default:100)
max_connections=256
# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)
# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0
# Do not cache results (default:1)
query_cache_type=0
# Do not use the privileges mechanisms
skip_grant_tables
# Do not listen for TCP/IP connections at all
skip_networking
# The number of open tables for all threads. (default:64)
table_open_cache=200
# How many threads the server should cache for reuse (default:0)
thread_cache_size=3
# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000
# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K
[client]
default-character-set=utf8
Test 7: SUCCESS
MySQL server custom configuration found.
Details: The custom configuration for the MySQL server was found and is readable at <a href='/home/the_user/.config/akonadi/mysql-local.conf'>/home/the_user/.config/akonadi/mysql-local.conf</a>
File content of '/home/the_user/.config/akonadi/mysql-local.conf':
# workaround fix for akonadi db error after server upgrade
# http://forum.kde.org/viewtopic.php?f=215&t=101004
[mysqld]
binlog_format=row
Test 8: SUCCESS
MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href='/home/the_user/.local/share/akonadi/mysql.conf'>/home/the_user/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/the_user/.local/share/akonadi/mysql.conf':
# Global Akonadi MySQL server settings,
# These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
# Based on advice by Kris KÃ¶hntopp <[email protected]>
[mysqld]
# strict query parsing/interpretation
# TODO: make Akonadi work with those settings enabled
# sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
# sql_mode=strict_trans_tables
# DEBUGGING:
# log all queries, useful for debugging but generates an enormous amount of data
# log=mysql.full
# log queries slower than n seconds, log file name relative to datadir (for debugging only)
# log_slow_queries=mysql.slow
# long_query_time=1
# log queries not using indices, debug only, disable for production use
# log_queries_not_using_indexes=1
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");
# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)
#expire_logs_days=3
#sync_bin_log=0
# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci
# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M
# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M
# Create a .ibd file for each table (default:0)
innodb_file_per_table=1
# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2
# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M
# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M
# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err
# print warnings and connection errors (default:1)
log_warnings=2
# Convert table named to lowercase
lower_case_table_names=1
# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M
# Maximum simultaneous connections allowed (default:100)
max_connections=256
# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)
# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0
# Do not cache results (default:1)
query_cache_type=0
# Do not use the privileges mechanisms
skip_grant_tables
# Do not listen for TCP/IP connections at all
skip_networking
# The number of open tables for all threads. (default:64)
table_open_cache=200
# How many threads the server should cache for reuse (default:0)
thread_cache_size=3
# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000
# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K
[client]
default-character-set=utf8
# workaround fix for akonadi db error after server upgrade
# http://forum.kde.org/viewtopic.php?f=215&t=101004
[mysqld]
binlog_format=row
Test 9: SUCCESS
akonadictl found and usable
Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.13.0
Test 10: SUCCESS
Akonadi control process registered at D-Bus.
Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.
Test 11: SUCCESS
Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.
Test 12: SKIP
Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.
Test 13: SUCCESS
Resource agents found.
Details: At least one resource agent has been found.
Directory listing of '/usr/share/akonadi/agents':
akonadibalooindexingagent.desktop
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
followupreminder.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
knutresource.desktop
kolabproxyresource.desktop
kolabresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share'
Test 14: ERROR
Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/the_user/.local/share/akonadi/akonadiserver.error'>/home/the_user/.local/share/akonadi/akonadiserver.error</a>.
File content of '/home/the_user/.local/share/akonadi/akonadiserver.error':
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
Test 15: ERROR
Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/the_user/.local/share/akonadi/akonadiserver.error.old'>/home/the_user/.local/share/akonadi/akonadiserver.error.old</a>.
File content of '/home/the_user/.local/share/akonadi/akonadiserver.error.old':
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
DATABASE ERROR:
Error code: 1062
DB error: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex'"
Error text: "Duplicate entry '93-INBOX' for key 'CollectionTable_parentAndNameIndex' QMYSQL3: Unable to execute statement"
Query: "INSERT INTO CollectionTable (remoteId, remoteRevision, name, parentId, resourceId, enabled, syncPref, displayPref, indexPref, cachePolicyInherit, isVirtual) VALUES (:0, :1, :2, :3, :4, :5, :6, :7, :8, :9, :10)"
Control process died, committing suicide!
Test 16: ERROR
Current Akonadi control error log found.
Details: The Akonadi control process reported errors during its current startup. The log can be found in <a href='/home/the_user/.local/share/akonadi/akonadi_control.error'>/home/the_user/.local/share/akonadi/akonadi_control.error</a>.
File content of '/home/the_user/.local/share/akonadi/akonadi_control.error':
Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder" could not be found!
Test 17: ERROR
Previous Akonadi control error log found.
Details: The Akonadi control process reported errors during its previous startup. The log can be found in <a href='/home/the_user/.local/share/akonadi/akonadi_control.error.old'>/home/the_user/.local/share/akonadi/akonadi_control.error.old</a>.
File content of '/home/the_user/.local/share/akonadi/akonadi_control.error.old':
Executable "akonadi_nepomuk_feeder" for agent "akonadi_nepomuk_feeder" could not be found!

After Upload you can delete the Duplicates comparing the employee Id.
It Will be Possible only when you use OLE and read the file records line by Line. I am not sure of the error Handling with OLE control. It may lead to some performance issues..

After upgrading to Yosemite (I don't have iPhoto anymore, only PHOTOS) my pictures will not import from my iPad or iPhone 5s or any picture from web, it shows "Database Error: failured to persist version"

After upgrading to Yosemite (I don't have iPhoto anymore, only PHOTOS) my pictures will not import from my iPad or iPhone 5s or any picture from web, it shows "Database Error: failured to persist version". Any help will be greatly appreciated.

Sorry,
Yes, the error message is exactly like that ("Database error: failured to persist version")
No photos will import at all. I use USB to import from iPhone 5s or iPad 2.
About the difference? iPhoto and Photos . Are there two softwares?
I also will like to merge and/or synchronize all my photos I had saved to iCloud backups, Macbook Pro, iPhone 5s and iPad hard drives using iPhoto. It's call iPhoto library. At one point I turned off streaming.
Thanks again Larry HN.

Database Error while running the query.

Hi,
While running the query in webi rich client i am having a "database error IES 10901 and WIS 10901" , it is showing that the data source name not found and default driver is not specified.
I am trying to generate report from efashion universe which is in .unx format, same client version and universe is running fine on another machine (webi rich client).
PS: The above mentioned universe is running fine on my BI launch pad, the problem is with webi rich client only.
Please help!!

Hi,
Which Database your are using .
As explained by Yuvraj You need to install driver for specific database .
Ask for client or (your Database ) driver from administrator .
After installation you can see your database Driver in following path
Control Panel\System and Security\Administrative Tools\Data Sources (ODBC)
See in Drivers Tab .
If you are using oracle & client is install on your system then Check TNS Names File in NETWORK folder .

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

While Refresh the report in webi i got database error.

Hi All,
I try to refresh the report in CMC i got database error . Can any one please help me how to resolve this.
Regards,
Arjun

Hi Mallikarujun,
Try selecting the values using show values for particular column in Universe.
If that is fine and you are using SQL Server then the query is returning more that 2147483647 which is the limit for the return count by SQL Server (4 Bytes).
There may be issue in join condition, if not try applying filter in query

Live office database errors in Citrix - underlying WebI reports work fine

Hi,
We have a live office report with 30 tabs in the excel file i.e. 30 webi report parts in it. It accesses 20 webi reports, each built on a BEX query.
Please see below the error which users get while running the report in Citrix environment. The underlying WebI report has no database errors, and we were able to run the Live Office reports at the same time on LAN. The Citirx users get these database/auth errors intermittently, on different tabs of the report at different times - the underlying BO reports are error free and users have proper rights to execute them.
"An error occured while opening the report. The report does not exist; youhave insufficient rights to open the report; or you cannot make a connection to the BusinessObjects Web Service. (LO 02010)
Failed to get the document information (LO 26315)
A database error occured. The database error text is: ...."
Please help.
Thanks,
Soumya

Hi,
BO Version is BO XI 3.1 SP2 FP2.1
Datasource - BEX queries BW Relese 701, support pack level 8
We have made users login to Infoview and checked that they are able to execute the WebI reports. Also, earlier they were able to run all reports, so there is no access problem.
These errors started occuring when we had to refersh BO Universes after some of the BEX queries changed. We even asked users to stop using the excel files on which they used to get errors, thinking the files may be corrupt. Then we sent them new files which we had successfully refershed at our end. But still they get these errors in their environment.
Please advise.
Thanks,
Soumya

Database Error while refreshing webi report

Hi,
I am getting following error while refreshing webi report. And also all my scheduled webi reports are getting failed because of same issue. What would be the reason for this error.
Regards,
PRK

Hi Praveen,
As you are getting error 'IES10901' it is related to database connection issue.
Find below link it might help you.
Database error in Web I ( BO 4.0)
check your universe connections to DB(ODBC connections).
Regards,
Samatha B.

Error while sending the mail( Database error for ADDR_PERS_COMP_COMM_GE)

Hello guys,
I am facing the error    " Database error for <ADDR_PERS_COMP_COMM_GET> <0> " as a pop-up message.
below is my program.
types: BEGIN OF t_p0002,
        pernr type PERSNO,       "Personnel number
        nachn TYPE PAD_NACHN,    "Last Name
        VORNA TYPE PAD_VORNA,    "First Name
        gbdat TYPE gbdat,        "Date of Birth
      END OF t_p0002.
*******************Data of an object which can be changed**************************************
data   S_maildata type SODOCCHGI1.
*******************Text field length 255: texts***********************************************
data : IT_MAILTXT1 type table of SOLISTI1 , "Internal table will contain texts of mail header
       WA_MAILTXT1 TYPE SOLISTI1,
       IT_MAILTXT2 type table of SOLISTI1 , "Internal table will contain texts of contents in the mail
       WA_MAILTXT2 TYPE SOLISTI1.
*******************Structure of the API Recipient List*****************************************
data : IT_MAILREC type table of SOMLRECI1,
       WA_MAILREC TYPE SOMLRECI1.
DATA : it_pa0002 TYPE TABLE OF t_p0002,
       wa_pa0002 type t_p0002.
data Header_text type c LENGTH 15.
CONSTANTS content_text type c LENGTH 35 VALUE 'Tomorrow is the birthday of'.
*******************Event start of selection***************************************************
start-of-selection.
PERFORM get_birthdate.   " will give birthday details
PERFORM document_details. " will give text and mail details
*&      Form get_birthdate
      text : subroutine to get employee birthdate details
form get_birthdate.
data : l_date like sy-datum.
refresh it_pa0002.
l_date = sy-datum + 1.
SELECT pernr nachn vorna gbdat
    from pa0002
    INTO TABLE it_pa0002
    where gbdat = '19650302'.
ENDFORM.                    "get_birthdate
*&      Form document_details
      text : subroutine to get texts and mail details.
FORM document_details.
CLEAR: Header_text,
          wa_MAILREC.
REFRESH IT_MAILREC.
S_maildata-obj_name = 'Birthday Reminder'.
s_maildata-obj_descr = 'Birthday Reminder'.
s_maildata-obj_langu = sy-langu.
READ TABLE IT_MAILTXT1 INTO WA_MAILTXT1
WITH KEY WA_MAILTXT1-line .
WA_MAILTXT1-line = 'Birthday Reminder'.
append WA_MAILTXT1 TO IT_MAILTXT1.
CLEAR WA_MAILTXT1.
LOOP at it_pa0002 INTO wa_pa0002.
    READ TABLE IT_MAILTXT2 INTO WA_MAILTXT2
     WITH KEY WA_MAILTXT2-line .
    CONCATENATE content_text ' ( ' wa_pa0002-pernr ' ) ' wa_pa0002-nachn wa_pa0002-vorna
    INTO WA_MAILTXT2 SEPARATED BY ' '.
    append WA_MAILTXT2 TO IT_MAILTXT2.
    CLEAR WA_MAILTXT2.
    CLEAR wa_pa0002.
ENDLOOP.
   LOOP AT IT_MAILREC INTO WA_MAILREC.
WA_MAILREC-RECEIVER = 'Any mail id'.
WA_MAILREC-rec_type = 'U'.
append WA_MAILREC TO IT_MAILREC.
   ENDLOOP.
********************Function Mofule:To Send new Document*****************************************
CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
EXPORTING
document_data = S_maildata
DOCUMENT_TYPE = 'RAW'
PUT_IN_OUTBOX = ' '
COMMIT_WORK = 'X'
IMPORTING
SENT_TO_ALL =
NEW_OBJECT_ID =
tables
OBJECT_HEADER = IT_MAILTXT1
OBJECT_CONTENT = IT_MAILTXT2
CONTENTS_HEX =
OBJECT_PARA =
OBJECT_PARB =
receivers = IT_MAILREC
   EXCEPTIONS
   TOO_MANY_RECEIVERS = 1
   DOCUMENT_NOT_SENT = 2
   DOCUMENT_TYPE_NOT_EXIST = 3
   OPERATION_NO_AUTHORIZATION = 4
   PARAMETER_ERROR = 5
   X_ERROR = 6
   ENQUEUE_ERROR = 7
   OTHERS = 8
IF sy-subrc = 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    "document_details
After I pressed the exit button the program is getting terminated but still this mail is comming to sost transaction code.
If I will comment the message code which is after sy-subrc the popup will not come and program will work without any interruption.
Can anybody please solve this problem?

Resolved

Database error 3997 at EXE in ECC 5.0

Hi,
I am getting this error in SAM system log "<b>Database error 3997</b>".
And the OS collector (RSCOLL00) is failling on peak time and its showing the same type of error " SQL error 3997".
Pls suggest me to solve this issues.
--gopi

Hi,
I am getting this error in SM21 system log "Database error 3997".
And the OS collector (RSCOLL00) is failling on peak time and its showing the same type of error " SQL error 3997".
Pls suggest me to solve this issues.
--gopi

Database error ZMM 3.0

Similar Messages

Maybe you are looking for