# How to catch "Access to DialectResolutionInfo" exception

**URL:** <https://discourse.hibernate.org/t/how-to-catch-access-to-dialectresolutioninfo-exception/4701>\
**Category:** Hibernate ORM\
**Created:** [October 28, 2020, 12:10pm UTC](https://discourse.hibernate.org/t/how-to-catch-access-to-dialectresolutioninfo-exception/4701 "2020-10-28T12:10:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sreejesh](https://avatars.discourse-cdn.com/v4/letter/s/9de0a6/32.png) [@sreejesh](https://discourse.hibernate.org/u/sreejesh)\
**Post date:** [October 28, 2020, 12:10pm UTC](https://discourse.hibernate.org/t/how-to-catch-access-to-dialectresolutioninfo-exception/4701/1 "2020-10-28T12:10:05Z")

</div>

How to catch “Access to DialectResolutionInfo cannot be null when ‘hibernate.dialect’ not set” exception ?

---

<div class="post-metadata">

**Author:** ![beikov](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.hibernate.org/beikov/32/258_2.png) [@beikov](https://discourse.hibernate.org/u/beikov)\
**Post date:** [November 4, 2020, 5:37pm UTC](https://discourse.hibernate.org/t/how-to-catch-access-to-dialectresolutioninfo-exception/4701/2 "2020-11-04T17:37:16Z")

</div>

This is usually the case when the database connection details you configured are not correct or the database is not reachable. Depending on the environment you are running in, it might not be possible to catch this. This is thrown during `EntityManagerFactory` creation which usually happens at boot time. By setting a dialect explicitly, you can delay the exception caused by the fact, that no connection can be acquired.