Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Unexpected error 0x10010000

Updated: 26 Dec 2011 | 32 comments
Simpson Homer's picture
Simpson Homer
Symantec Employee
+3 3 Votes
Login to vote
This issue has been solved. See solution.

Unexpected error 0x10010000 Upgraded from 11.0.6 to 12.1 

Discussion Filed Under:
, , , ,

Comments

Thomas K's picture
01
Dec
2011
2 Votes +2
Login to vote
Thomas K
Admin
Accredited

What database are you using?

What database are you using? Is the DB external? When does the error pop up?

Simpson Homer's picture
01
Dec
2011
2 Votes +2
Login to vote
Simpson Homer
Symantec Employee

SQL database external

SQL database external

Thomas K's picture
01
Dec
2011
2 Votes +2
Login to vote
Thomas K
Admin
Accredited

Make sure you log into the

Make sure you log into the SEPM using a user account that has full rights to access both the SEPM and the external SQL database.

http://www.symantec.com/business/support/index?pag...

Simpson Homer's picture
01
Dec
2011
2 Votes +2
Login to vote
Simpson Homer
Symantec Employee

The login has all the rights,

The login has all the rights, using Windows authentication.

Thomas K's picture
01
Dec
2011
2 Votes +2
Login to vote
Thomas K
Admin
Accredited

Are there special characters

Are there special characters in the name? There was an issue, and the solution was to change to SA authentication from Windows authentication.

Simpson Homer's picture
01
Dec
2011
2 Votes +2
Login to vote
Simpson Homer
Symantec Employee

No special character in the

No special character in the User name of SQL

anup_Kothurkar's picture
01
Dec
2011
0 Votes 0
Login to vote
anup_Kothurkar
Symantec Employee
Accredited

On the Login Screen try

On the Login Screen try to replace the name of server to localhost.

Chetan Savade's picture
02
Dec
2011
0 Votes 0
Login to vote
Chetan Savade
Technical Support

Hi, I hope disk space is not

Hi,

I hope disk space is not causing this issue.

Thanks and Regards, 

Chetan Savade

Technical Support Analyst,

End Point Security, Enterprise Technical Support

pete_4u2002's picture
02
Dec
2011
0 Votes 0
Login to vote
pete_4u2002
Symantec Employee

pass on the scm-server-0.log

pass on the scm-server-0.log

Cheers!
Pete

Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619

ArpitBadwaik's picture
02
Dec
2011
1 Vote -1
Login to vote
ArpitBadwaik
Symantec Employee
Accredited

Hi,

Log into the SEPM using a user account that has full rights to access both the SEPM and the external SQL database.

Change the Windows Authentication to SQL authentication using the Management Server Configuration Wizard.

Cause:The user account being used was not able to authenticate to the external SQL database.

Try this it might help you.

In the SEPM configuration to SQL, change to SA authentification from Windows authentication and it solved the issue.

 

  1. In SQL Server Management Studio Object Explorer, right-click the server, and then click Properties.

  2. On the Security page, under Server authentication, select the new server authentication mode, and then click OK.

  3. In the SQL Server Management Studio dialog box, click OK to acknowledge the requirement to restart SQL Server.

 Arpit Badwaik

Symantec Technical Support Analyst, SEP

MCITP

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you

Simpson Homer's picture
02
Dec
2011
1 Vote +1
Login to vote
Simpson Homer
Symantec Employee

  On the Login Screen try

 

On the Login Screen try to replace the name of server to localhost.: Done That, Didn't help.

disk space is not causing this issue.

Already using Windows Authentication.

    Simpson Homer's picture
    02
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

      11-12-02 09:05:26.999

     

    11-12-02 09:05:26.999 THREAD 1 SEVERE: ================== Server Environment ===================
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: os.name = Windows 2003
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: os.version = 5.2
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: os.arch = x86
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.version = 1.6.0_24
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.vm.version = 19.1-b02
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.home = E:\Program Files\Symantec\Symantec Endpoint Protection Manager\jre
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: catalina.home = E:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: java.user = null
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: user.language = en
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: user.country = US
    2011-12-02 09:05:26.999 THREAD 1 SEVERE: scm.server.version = 12.1.671.4971
    2011-12-02 09:05:28.405 THREAD 1 SEVERE: Database Schema Version = 12.1.0.3
    2011-12-02 09:05:29.452 THREAD 1 SEVERE: License state = SEPE_TRIAL
    2011-12-02 09:05:29.452 THREAD 1 SEVERE: License status on SEPM = Good
    2011-12-02 09:05:29.452 THREAD 1 SEVERE: resetAgentOfflineState=true
    2011-12-02 09:05:29.483 THREAD 1 SEVERE: ================== StartClientTransport ===================
    2011-12-02 09:05:29.483 THREAD 1 SEVERE: [1] Initializing Tomcat ClientTransport Key for Secars...
    2011-12-02 09:05:29.499 THREAD 1 SEVERE: startClientTransport>>resetAgentToOfflineState=true
    2011-12-02 09:05:29.499 THREAD 1 SEVERE: startClientTransport>>start set agent offline
    2011-12-02 09:05:29.640 THREAD 1 SEVERE: Schedule is started!
    2011-12-02 09:05:29.671 THREAD 1 SEVERE: SEPM Service started
    2011-12-02 09:05:31.624 THREAD 25 WARNING: No status. Recompile all groups.
    2011-12-02 09:06:01.506 THREAD 39 WARNING: Error during AV record processing: no associated scan start found for scan stop event
    Simpson Homer's picture
    02
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    Even after doing a fresh

    Even after doing a fresh install, the error remains constant. Would upgrading to 12.1 help?

    ArpitBadwaik's picture
    02
    Dec
    2011
    3 Votes +1
    Login to vote
    ArpitBadwaik
    Symantec Employee
    Accredited

    Hi, Please check the ODBC

    Hi,

    Please check the ODBC connection if you are able to get through it add the user which pass the ODBC connection to SQL server its the problem with Authentication nothing else.

     Arpit Badwaik

    Symantec Technical Support Analyst, SEP

    MCITP

    Don't forget to mark your thread as 'SOLVED' with the answer that best helped you

    Simpson Homer's picture
    02
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    Gets through..

    Gets through..

    Swapnil's picture
    02
    Dec
    2011
    1 Vote +1
    Login to vote
    Swapnil
    Accredited

    This is an issue with

    This is an issue with Manifest if this machine is server 2008 ...

    http://www.symantec.com/business/support/index?page=content&id=TECH105218

    Swapnil

    SOC Team .

    Please don't forget to mark your thread solved with whatever answer helped you.

    Swapnil's picture
    02
    Dec
    2011
    1 Vote +1
    Login to vote
    Swapnil
    Accredited

    This is an issue with IIS

    This is an issue with IIS which i have experienced though sep upgrade 11.0.6 to 12.1 it still use IIS for service location hence results in this error usually can be found on groups or which crating a group or first 3 tab goes with error 403

    Swapnil

    SOC Team .

    Please don't forget to mark your thread solved with whatever answer helped you.

    Simpson Homer's picture
    02
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    but no errors found!

    but no errors found!

    Swapnil's picture
    02
    Dec
    2011
    1 Vote +1
    Login to vote
    Swapnil
    Accredited

    check config.log

    check config.log

    Swapnil

    SOC Team .

    Please don't forget to mark your thread solved with whatever answer helped you.

    Simpson Homer's picture
    05
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    I cannot find that file..

    I cannot find that file.. Plus i think i found a resolution...

    I'm now getting wireshark logs.

    Simpson Homer's picture
    06
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    ArpitBadwaik   Why would you

    ArpitBadwaik

     

    Why would you recommend to change the authetication level? Windows authentication works fine and even allows to login into the SQL server.

    Simpson Homer's picture
    09
    Dec
    2011
    0 Votes 0
    Login to vote
    Simpson Homer
    Symantec Employee

    No update?

    No update?

    Ghent's picture
    09
    Dec
    2011
    0 Votes 0
    Login to vote
    Ghent
    Symantec Employee
    Accredited

    Any hard data?

    Could you provide some solid data, like a screen shot?
    Also, search the log files and post an except that contains the error you have mentioned.

    Logs should be located in either %SEPM%\tomcat\logs, %SEPM\apache\logs or %SEPM%\data\inbox\log\exsecars.log

    Simpson Homer's picture
    12
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

     When we use Windows

     When we use Windows Authentication, it does not work and when we use SA authentication, it works just fine and we are able to login in SEPM without any errors... But why??

    pete_4u2002's picture
    12
    Dec
    2011
    0 Votes 0
    Login to vote
    pete_4u2002
    Symantec Employee

    are these machines in the

    are these machines in the same domain?

    Cheers!
    Pete

    Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619

    Simpson Homer's picture
    12
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    Yes Pete, they belong to the

    Yes Pete, they belong to the same domain... also its a remote SQL on a Windows 2003 machine, but in the same domain.

    Simpson Homer's picture
    21
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    Pete.. any other sugesstions?

    Pete.. any other sugesstions?

    Ghent's picture
    21
    Dec
    2011
    0 Votes 0
    Login to vote
    Ghent
    Symantec Employee
    Accredited

    How about the upgrade.log file?

    I'm unclear what you are actually seeing, but if you see this error during the database upgrade wizard, you may want to check (and post) the upgrade.log file. If the is an error from SQL normally there is a line of text in the Upgrade log that says something to the effect of, "The SQL error code is X".

    Simpson Homer's picture
    22
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    I do not have the upgrade.log

    I do not have the upgrade.log file, but do have the SQL logs.

    AttachmentSize
    SQLServerErrorLog.txt 46.76 KB
    Ghent's picture
    22
    Dec
    2011
    0 Votes 0
    Login to vote
    Ghent
    Symantec Employee
    Accredited

    Errors and Logs

    No Upgrade.log? Now I'm really confuse... at what point do you see this error? Would you happen to have a screen shot?

    Is it during the MSI phase, Java Configuration Wizard, Java DB Upgrade, or Console Login phase? A Screen shot should help answer that question.

    Well, I see errors in your SQLServerErrorLog.txt, but of course, I have no idea what the login for your SEP product is, but it if by chance happens to be 'COG-SYMANTEC$', have you checked articles like these ones?
    http://www.eraofdata.com/blog/sql-18456-login-fail...

    State 11 errors seem a little tricky -- but it seems to be a permissions problem with either SQL itself, or between SQL and Active Directory.

    Simpson Homer's picture
    23
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    What kind of screen shot

    What kind of screen shot would you want? And when you say permissions what kinda permissions are missing?

    Simpson Homer's picture
    26
    Dec
    2011
    1 Vote +1
    Login to vote
    Simpson Homer
    Symantec Employee

    Works with SQL

    Works with SQL authentication, but fails with Windows.. was working fine till version 11.0

    But problems in 12.1 Would be using SQL authentication for now.. :(

    SOLUTION

    Technical Support

    Symantec.com

    Store

    Community Stats

    Total Content Items
    Members
    270,002