Erro tragico

4 respostas
Sleipbr

alguém sabe porque ta dando esse erro?

<blockquote>Out 22, 2012 12:21:04 AM org.hibernate.cfg.Environment 

Informações: Hibernate 3.2.5

Out 22, 2012 12:21:04 AM org.hibernate.cfg.Environment 

Informações: hibernate.properties not found

Out 22, 2012 12:21:04 AM org.hibernate.cfg.Environment buildBytecodeProvider

Informações: Bytecode provider name : cglib

Out 22, 2012 12:21:04 AM org.hibernate.cfg.Environment 

Informações: using JDK 1.4 java.sql.Timestamp handling

Out 22, 2012 12:21:04 AM org.hibernate.cfg.Configuration configure

Informações: configuring from resource: /hibernate.cfg.xml

Out 22, 2012 12:21:04 AM org.hibernate.cfg.Configuration getConfigurationInputStream

Informações: Configuration resource: /hibernate.cfg.xml

Out 22, 2012 12:21:04 AM org.hibernate.cfg.Configuration addResource

Informações: Reading mappings from resource : Cliente.hbm.xml

Out 22, 2012 12:21:04 AM org.hibernate.cfg.HbmBinder bindRootPersistentClassCommonValues

Informações: Mapping class: supermercado.uteis.classesPersistentes.Cliente -> Cliente

Out 22, 2012 12:21:04 AM org.hibernate.cfg.Configuration doConfigure

Informações: Configured SessionFactory: null

Out 22, 2012 12:21:04 AM org.hibernate.connection.DriverManagerConnectionProvider configure

Informações: Using Hibernate built-in connection pool (not for production use!)

Out 22, 2012 12:21:04 AM org.hibernate.connection.DriverManagerConnectionProvider configure

Informações: Hibernate connection pool size: 20

Out 22, 2012 12:21:04 AM org.hibernate.connection.DriverManagerConnectionProvider configure

Informações: autocommit mode: false

Out 22, 2012 12:21:04 AM org.hibernate.connection.DriverManagerConnectionProvider configure

Advertência: no JDBC Driver class was specified by property hibernate.connection.driver_class

Out 22, 2012 12:21:04 AM org.hibernate.connection.DriverManagerConnectionProvider configure

Informações: using driver: null at URL: jdbc:sqlserver://CESAR-4E3FFDD6F\SQLEXPRESS:1433;databaseName=supermercado

Out 22, 2012 12:21:04 AM org.hibernate.connection.DriverManagerConnectionProvider configure

Informações: connection properties: {class=com.microsoft.sqlserver.jdbc.SQLServerDriver}

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Advertência: Could not obtain connection metadata

com.microsoft.sqlserver.jdbc.SQLServerException: Falha de logon do usuário ‘’. O usuário não está associado a uma conexão confiável com o SQL Server.

at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:197)

at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:246)

at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:83)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:2529)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:1905)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(SQLServerConnection.java:41)

at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:1893)

at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1045)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:817)

at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:700)

at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:842)

at java.sql.DriverManager.getConnection(DriverManager.java:579)

at java.sql.DriverManager.getConnection(DriverManager.java:190)

at org.hibernate.connection.DriverManagerConnectionProvider.getConnection(DriverManagerConnectionProvider.java:110)

at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:84)

at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2009)

at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1292)

at supermercado.uteis.TesteCliente.main(TesteCliente.java:14)
Out 22, 2012 12:21:18 AM org.hibernate.dialect.Dialect 

Informações: Using dialect: org.hibernate.dialect.SQLServerDialect

Out 22, 2012 12:21:18 AM org.hibernate.transaction.TransactionFactoryFactory buildTransactionFactory

Informações: Using default transaction strategy (direct JDBC transactions)

Out 22, 2012 12:21:18 AM org.hibernate.transaction.TransactionManagerLookupFactory getTransactionManagerLookup

Informações: No TransactionManagerLookup configured (in JTA environment, use of read-write or transactional second-level cache is not recommended)

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Automatic flush during beforeCompletion(): disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Automatic session close at end of transaction: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Scrollable result sets: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: JDBC3 getGeneratedKeys(): disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Connection release mode: auto

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Default batch fetch size: 1

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Generate SQL with comments: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Order SQL updates by primary key: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Order SQL inserts for batching: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory createQueryTranslatorFactory

Informações: Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory

Out 22, 2012 12:21:18 AM org.hibernate.hql.ast.ASTQueryTranslatorFactory 

Informações: Using ASTQueryTranslatorFactory

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Query language substitutions: {}

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: JPA-QL strict compliance: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Second-level cache: enabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Query cache: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory createCacheProvider

Informações: Cache provider: org.hibernate.cache.NoCacheProvider

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Optimize cache for minimal puts: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Structured second-level cache entries: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Statistics: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Deleted entity synthetic identifier rollback: disabled

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Default entity-mode: pojo

Out 22, 2012 12:21:18 AM org.hibernate.cfg.SettingsFactory buildSettings

Informações: Named query checking : enabled

Out 22, 2012 12:21:18 AM org.hibernate.impl.SessionFactoryImpl 

Informações: building session factory

Out 22, 2012 12:21:18 AM org.hibernate.impl.SessionFactoryObjectFactory addInstance

Informações: Not binding factory to JNDI, no JNDI name configured

Out 22, 2012 12:21:33 AM org.hibernate.util.JDBCExceptionReporter logExceptions

Advertência: SQL Error: 18452, SQLState: S0001

Out 22, 2012 12:21:33 AM org.hibernate.util.JDBCExceptionReporter logExceptions

Grave: Falha de logon do usuário ‘’. O usuário não está associado a uma conexão confiável com o SQL Server.

</blockquote>

4 Respostas

Sleipbr

conseguir identificar.

asandrob

Show de bola, que bom que conseguiu identificar.
Agora descreve a solução!!!

Hebert_Coelho

asandrob:
Show de bola, que bom que conseguiu identificar.
Agora descreve a solução!!!
+1

Sleipbr

Eu fui no SQL Server Configuration Manager reiniciei os serviços do sql server e dei um clear and build no projeto…Depois disso funcionou direitinho!

Criado 21 de outubro de 2012
Ultima resposta 22 de out. de 2012
Respostas 4
Participantes 3