Knowledge Partner
Knowledge Partner
1019 views

DAAS Error 486 when testing a JDBC Collector

Defined a JDBC collector for an Account.

I think I have everything correct, in terms of port, host, DB name, etc.
I can telnet from IDG server to the port on the DB server.

[FINE] 2018-08-21 12:20:20
com.netiq.iac.server.common.rest.RestCallExecutor$Request <init> -
[IG-SERVER]
DELETE
https://idgov.acme.edu:8443/daas/rest/service/JDBCSQLServerAccountTemplate-1534867912037-gromitid-8
Credentials: iac-service:********
Token: 21Aug2018 12:21:46 CDT
eH8AIIPeMI0eGjG2V5gSabc@rQyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oF
hFERX9emwoo@vvp
Headers:
X-Authorization : Bearer
eH8AIIPeMI0eGjG2V5gSbl@abcyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oFhFERX9emwoo@vvp
[FINE] 2018-08-21 12:20:20
com.netiq.iac.persistence.service.cum.DataCollectionService
testConnection - [IG-SERVER] Encountered unexpected error: DAAS_ERROR:
486 : Target Connection failure.
com.netiq.common.i18n.LocalizedException: Encountered unexpected error:
DAAS_ERROR: 486 : Target Connection failure.


Do we have access to a list of DaaS error codes?

DaaS is Directory As a Service I would guess. There is a daas.war...
Guess go look and see what is in that expanded WAR file inside the
tomcat\webapps folder.
0 Likes
14 Replies
Micro Focus Expert
Micro Focus Expert

Re: DAAS Error 486 when testing a JDBC Collector

On 8/21/18 1:29 PM, Geoffrey Carman wrote:
> Defined a JDBC collector for an Account.
>
> I think I have everything correct, in terms of port, host, DB name, etc.
>  I can telnet from IDG server to the port on the DB server.
>
> [FINE] 2018-08-21 12:20:20
> com.netiq.iac.server.common.rest.RestCallExecutor$Request <init> -
> [IG-SERVER]
> DELETE
> https://idgov.acme.edu:8443/daas/rest/service/JDBCSQLServerAccountTemplate-1534867912037-gromitid-8
>
> Credentials: iac-service:********
> Token: 21Aug2018 12:21:46 CDT
> eH8AIIPeMI0eGjG2V5gSabc@rQyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oF
>
> hFERX9emwoo@vvp
> Headers:
>         X-Authorization : Bearer
> eH8AIIPeMI0eGjG2V5gSbl@abcyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oFhFERX9emwoo@vvp
>
> [FINE] 2018-08-21 12:20:20
> com.netiq.iac.persistence.service.cum.DataCollectionService
> testConnection - [IG-SERVER] Encountered unexpected error: DAAS_ERROR:
> 486 : Target Connection failure.
> com.netiq.common.i18n.LocalizedException: Encountered unexpected error:
> DAAS_ERROR: 486 : Target Connection failure.
>
>
> Do we have access to a list of DaaS error codes?
>
> DaaS is Directory As a Service I would guess. There is a daas.war...
> Guess go look and see what is in that expanded WAR file inside the
> tomcat\webapps folder.

Greetings,
With the impression that you are receiving this when pressing the
Test Connection button

1) Did you supply the correct User ID and Password to connect?

2) If the database is not MS SQL (based upon other thread where you are
using MS SQL), did you add the necessary jar(s) to the tomcat/lib
directory for the DB server in question and restart Tomcat?

*Since you are on Linux are the jar(s) set to the correct ownership?



--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector

On 8/21/2018 5:05 PM, Steven Williams wrote:
> On 8/21/18 1:29 PM, Geoffrey Carman wrote:
>> Defined a JDBC collector for an Account.
>>
>> I think I have everything correct, in terms of port, host, DB name,
>> etc.   I can telnet from IDG server to the port on the DB server.
>>
>> [FINE] 2018-08-21 12:20:20
>> com.netiq.iac.server.common.rest.RestCallExecutor$Request <init> -
>> [IG-SERVER]
>> DELETE
>> https://idgov.acme.edu:8443/daas/rest/service/JDBCSQLServerAccountTemplate-1534867912037-gromitid-8
>>
>> Credentials: iac-service:********
>> Token: 21Aug2018 12:21:46 CDT
>> eH8AIIPeMI0eGjG2V5gSabc@rQyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oF
>>
>> hFERX9emwoo@vvp
>> Headers:
>>          X-Authorization : Bearer
>> eH8AIIPeMI0eGjG2V5gSbl@abcyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oFhFERX9emwoo@vvp
>>
>> [FINE] 2018-08-21 12:20:20
>> com.netiq.iac.persistence.service.cum.DataCollectionService
>> testConnection - [IG-SERVER] Encountered unexpected error: DAAS_ERROR:
>> 486 : Target Connection failure.
>> com.netiq.common.i18n.LocalizedException: Encountered unexpected
>> error: DAAS_ERROR: 486 : Target Connection failure.
>>
>>
>> Do we have access to a list of DaaS error codes?
>>
>> DaaS is Directory As a Service I would guess. There is a daas.war...
>> Guess go look and see what is in that expanded WAR file inside the
>> tomcat\webapps folder.

> Greetings,
>    With the impression that you are receiving this when pressing the
> Test Connection button
>
> 1) Did you supply the correct User ID and Password to connect?


I am informed they are correct, I did not recieve them, so I cannot
confirm. I also assume they got the DB name correct.

> 2) If the database is not MS SQL (based upon other thread where you are
> using MS SQL), did you add the necessary jar(s) to the tomcat/lib
> directory for the DB server in question and restart Tomcat?


Yes, it is MS-SQL, so no need for a new JAR I think.


> *Since you are on Linux are the jar(s) set to the correct ownership?


Since it works for the main connectivity, seems unlikely this would matter.

I guess the key take away is that the error 486 is not info, and it
would be super useful if more error messaging bubbled up to the logs at
least.

Is there a log level I could enable that would show more info on the
error?



0 Likes
Micro Focus Expert
Micro Focus Expert

Re: DAAS Error 486 when testing a JDBC Collector

On 8/21/18 5:29 PM, Geoffrey Carman wrote:
> On 8/21/2018 5:05 PM, Steven Williams wrote:
>> On 8/21/18 1:29 PM, Geoffrey Carman wrote:
>>> Defined a JDBC collector for an Account.
>>>
>>> I think I have everything correct, in terms of port, host, DB name,
>>> etc.   I can telnet from IDG server to the port on the DB server.
>>>
>>> [FINE] 2018-08-21 12:20:20
>>> com.netiq.iac.server.common.rest.RestCallExecutor$Request <init> -
>>> [IG-SERVER]
>>> DELETE
>>> https://idgov.acme.edu:8443/daas/rest/service/JDBCSQLServerAccountTemplate-1534867912037-gromitid-8
>>>
>>> Credentials: iac-service:********
>>> Token: 21Aug2018 12:21:46 CDT
>>> eH8AIIPeMI0eGjG2V5gSabc@rQyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oF
>>>
>>> hFERX9emwoo@vvp
>>> Headers:
>>>          X-Authorization : Bearer
>>> eH8AIIPeMI0eGjG2V5gSbl@abcyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oFhFERX9emwoo@vvp
>>>
>>> [FINE] 2018-08-21 12:20:20
>>> com.netiq.iac.persistence.service.cum.DataCollectionService
>>> testConnection - [IG-SERVER] Encountered unexpected error:
>>> DAAS_ERROR: 486 : Target Connection failure.
>>> com.netiq.common.i18n.LocalizedException: Encountered unexpected
>>> error: DAAS_ERROR: 486 : Target Connection failure.
>>>
>>>
>>> Do we have access to a list of DaaS error codes?
>>>
>>> DaaS is Directory As a Service I would guess. There is a daas.war...
>>> Guess go look and see what is in that expanded WAR file inside the
>>> tomcat\webapps folder.

>> Greetings,
>>     With the impression that you are receiving this when pressing the
>> Test Connection button
>>
>> 1) Did you supply the correct User ID and Password to connect?

>
> I am informed they are correct, I did not recieve them, so I cannot
> confirm.  I also assume they got the DB name correct.
>
>> 2) If the database is not MS SQL (based upon other thread where you
>> are using MS SQL), did you add the necessary jar(s) to the tomcat/lib
>> directory for the DB server in question and restart Tomcat?

>
> Yes, it is MS-SQL, so no need for a new JAR I think.
>
>
>> *Since you are on Linux are the jar(s) set to the correct ownership?

>
> Since it works for the main connectivity, seems unlikely this would matter.
>
> I guess the key take away is that the error 486 is not info, and it
> would be super useful if more error messaging bubbled up to the logs at
> least.
>
> Is there a log level I could enable that would show more info on the error?
>
>
>

Greetings,
I always suggest testing the connections outside of ID Gov with a
tool or stand alone java to ensure they are correct before trying to
utilize them within ID Gov.

--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector

>> Is there a log level I could enable that would show more info on the
>> error?


Enabling com.netiq.daas logging made it clearer where the issue was.

>    I always suggest testing the connections outside of ID Gov with a
> tool or stand alone java to ensure they are correct before trying to
> utilize them within ID Gov.


In this case we switched from the MS JDBC jar to the JTDS because we
were using Integrated Aauth in SQL and the account was a Domain account
not a DB account. This worked in the JTDS but not MS JDBC connectors.


0 Likes
Micro Focus Expert
Micro Focus Expert

Re: DAAS Error 486 when testing a JDBC Collector

On 8/24/18 7:24 AM, Geoffrey Carman wrote:
>>> Is there a log level I could enable that would show more info on the
>>> error?

>
> Enabling com.netiq.daas logging made it clearer where the issue was.
>
>>     I always suggest testing the connections outside of ID Gov with a
>> tool or stand alone java to ensure they are correct before trying to
>> utilize them within ID Gov.

>
> In this case we switched from the MS JDBC jar to the JTDS because we
> were using Integrated Aauth in SQL and the account was a Domain account
> not a DB account.  This worked in the JTDS but not MS JDBC connectors.
>
>

Greetings,
If you are using the jTDS jar instead of the MS SQL jar, then you
would need to utilize the JDBC (Account or Permission) jTDS collectors
and not the database specific one (in your case SQL Server)

--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector

On 8/24/2018 9:21 AM, Steven Williams wrote:
> On 8/24/18 7:24 AM, Geoffrey Carman wrote:
>>>> Is there a log level I could enable that would show more info on the
>>>> error?

>>
>> Enabling com.netiq.daas logging made it clearer where the issue was.
>>
>>>     I always suggest testing the connections outside of ID Gov with a
>>> tool or stand alone java to ensure they are correct before trying to
>>> utilize them within ID Gov.

>>
>> In this case we switched from the MS JDBC jar to the JTDS because we
>> were using Integrated Aauth in SQL and the account was a Domain
>> account not a DB account.  This worked in the JTDS but not MS JDBC
>> connectors.
>>
>>

> Greetings,
>    If you are using the jTDS jar instead of the MS SQL jar, then you
> would need to utilize the JDBC  (Account or Permission) jTDS collectors
> and not the database specific one (in your case SQL Server)


Ever listen to the Royal Canadian Air Farce radio comedy show? They had
a character who would always say some double entendre to a lady, to
which the response was, "She misconstrued... When I regained
consciousness").

https://www.youtube.com/watch?v=L9Sli10xGlg (Entire episode, the
specific moment at 53:00 or so. Alas, he says "She misunderstood" in
this one, but the rest is there.


Anyway you misconstrue.

Agreed I was not suggesting otherwise.

I started wiith the MS SQL template which hard codes/hides the proper class.

Then tried Generic JDBC specifying JTDS and was clearing missing some
parameters.

Then moved on to JTDS Template collector which just worked.



0 Likes
Micro Focus Expert
Micro Focus Expert

Re: DAAS Error 486 when testing a JDBC Collector

On 8/24/18 10:29 AM, Geoffrey Carman wrote:
> On 8/24/2018 9:21 AM, Steven Williams wrote:
>> On 8/24/18 7:24 AM, Geoffrey Carman wrote:
>>>>> Is there a log level I could enable that would show more info on
>>>>> the error?
>>>
>>> Enabling com.netiq.daas logging made it clearer where the issue was.
>>>
>>>>     I always suggest testing the connections outside of ID Gov with
>>>> a tool or stand alone java to ensure they are correct before trying
>>>> to utilize them within ID Gov.
>>>
>>> In this case we switched from the MS JDBC jar to the JTDS because we
>>> were using Integrated Aauth in SQL and the account was a Domain
>>> account not a DB account.  This worked in the JTDS but not MS JDBC
>>> connectors.
>>>
>>>

>> Greetings,
>>     If you are using the jTDS jar instead of the MS SQL jar, then you
>> would need to utilize the JDBC  (Account or Permission) jTDS
>> collectors and not the database specific one (in your case SQL Server)

>
> Ever listen to the Royal Canadian Air Farce radio comedy show? They had
> a character who would always say some double entendre to a lady, to
> which the response was, "She misconstrued... When I regained
> consciousness").
>
> https://www.youtube.com/watch?v=L9Sli10xGlg  (Entire episode, the
> specific moment at 53:00 or so.  Alas, he says "She misunderstood" in
> this one, but the rest is there.
>
>
> Anyway you misconstrue.
>
> Agreed I was not suggesting otherwise.
>
> I started wiith the MS SQL template which hard codes/hides the proper
> class.
>
> Then tried Generic JDBC specifying JTDS and was clearing missing some
> parameters.
>
> Then moved on to JTDS Template collector which just worked.
>
>
>

Greetings,
Just as a side note, please be aware that from an ID Gov core
perspective it is required to be using the MS SQL JDBC driver when it
(ID Gov) is utilizing MS SQL.

--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector


>> Then tried Generic JDBC specifying JTDS and was clearing missing some
>> parameters.
>>
>> Then moved on to JTDS Template collector which just worked.
>>
>>
>>

> Greetings,
>    Just as a side note, please be aware that from an ID Gov core
> perspective it is required to be using the MS SQL JDBC driver when it
> (ID Gov) is utilizing MS SQL.


Hmm... How do you configure the MS SQL JDBC driver for integrated auth,
when the login account isa domain account and not a DB account?

0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector

On 2018-08-21 19:29, Geoffrey Carman wrote:
> Defined a JDBC collector for an Account.
>
> I think I have everything correct, in terms of port, host, DB name, etc.
>  I can telnet from IDG server to the port on the DB server.
>
> [FINE] 2018-08-21 12:20:20
> com.netiq.iac.server.common.rest.RestCallExecutor$Request <init> -
> [IG-SERVER]
> DELETE
> https://idgov.acme.edu:8443/daas/rest/service/JDBCSQLServerAccountTemplate-1534867912037-gromitid-8
>
> Credentials: iac-service:********
> Token: 21Aug2018 12:21:46 CDT
> eH8AIIPeMI0eGjG2V5gSabc@rQyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oF
>
> hFERX9emwoo@vvp
> Headers:
>         X-Authorization : Bearer
> eH8AIIPeMI0eGjG2V5gSbl@abcyp6R@tVs5DveOPw0AhopXK302tqHTHgsMQ1TrZ8ZJWCdstsD/amVSRD1u7rffIVrCUmMn8s85PxZsD3wrm0hU3ZVAm2s9TVIXBIIvhdxmEm2pPP1WV8Fd4dmBZKHfXgOgGzuE6oFhFERX9emwoo@vvp
>
> [FINE] 2018-08-21 12:20:20
> com.netiq.iac.persistence.service.cum.DataCollectionService
> testConnection - [IG-SERVER] Encountered unexpected error: DAAS_ERROR:
> 486 : Target Connection failure.
> com.netiq.common.i18n.LocalizedException: Encountered unexpected error:
> DAAS_ERROR: 486 : Target Connection failure.
>
>
> Do we have access to a list of DaaS error codes?
>
> DaaS is Directory As a Service I would guess. There is a daas.war...
> Guess go look and see what is in that expanded WAR file inside the
> tomcat\webapps folder.

You can edit daas-logging.xml in the tomcat/conf folder and restart
Tomcat after changing INFO to TRACE.

--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.
0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector

>> [FINE] 2018-08-21 12:20:20
>> com.netiq.iac.persistence.service.cum.DataCollectionService
>> testConnection - [IG-SERVER] Encountered unexpected error: DAAS_ERROR:
>> 486 : Target Connection failure.
>> com.netiq.common.i18n.LocalizedException: Encountered unexpected
>> error: DAAS_ERROR: 486 : Target Connection failure.
>>
>>
>> Do we have access to a list of DaaS error codes?
>>
>> DaaS is Directory As a Service I would guess. There is a daas.war...
>> Guess go look and see what is in that expanded WAR file inside the
>> tomcat\webapps folder.

> You can edit daas-logging.xml in the tomcat/conf folder and restart
> Tomcat after changing INFO to TRACE.


An excellent point! I forgot about that! Two logging classes offered,
but parents...

com.microfocus.daas
com.netiq.daas

That is the hint I was looking for, thanks Alekz! I should have thought
of that on my own.

0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector

On 8/22/2018 7:08 AM, Geoffrey Carman wrote:
>>> [FINE] 2018-08-21 12:20:20
>>> com.netiq.iac.persistence.service.cum.DataCollectionService
>>> testConnection - [IG-SERVER] Encountered unexpected error:
>>> DAAS_ERROR: 486 : Target Connection failure.
>>> com.netiq.common.i18n.LocalizedException: Encountered unexpected
>>> error: DAAS_ERROR: 486 : Target Connection failure.
>>>
>>>
>>> Do we have access to a list of DaaS error codes?
>>>
>>> DaaS is Directory As a Service I would guess. There is a daas.war...
>>> Guess go look and see what is in that expanded WAR file inside the
>>> tomcat\webapps folder.

>> You can edit daas-logging.xml in the tomcat/conf folder and restart
>> Tomcat after changing INFO to TRACE.

>
> An excellent point! I forgot about that!  Two logging classes offered,
> but parents...
>
> com.microfocus.daas
> com.netiq.daas
>
> That is the hint I was looking for, thanks Alekz!  I should have thought
> of that on my own.


And we see with this logging enabled:

[FINE] 2018-08-22 08:31:00 com.netiq.daas.daaservice.ServiceProviderMap
clean - [DAAS] Collection cleaner running...
[FINE] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.ConnectorFactory createConnector -
[DAAS] Creating Microsoft SQLServer Specific Connector
[FINE] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.connector.DBConnector
setDriverClassName - [DAAS] Driver Class Name
com.microsoft.sqlserver.jdbc.SQLServerDriver
[FINE] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.connector.DBConnector
setConnectionProperties - [DAAS] setting connectionProperties
[FINE] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.connector.DBConnector
setConnectionProperties - [DAAS] Key :databaseName value 'Test' added to
connectionProperties
[FINE] 2018-08-22 08:31:00 com.netiq.daas.common.SrvInstance <init> -
[DAAS] New service instance. TTL: 60
[FINE] 2018-08-22 08:31:00 com.netiq.daas.common.SrvInstance
resetTimeout - [DAAS] Reset timeout for service instance to TTL: 60
[FINE] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.connector.DBConnector
setConnectionProperties - [DAAS] setting connectionProperties
[FINE] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.connector.DBConnector
setConnectionProperties - [DAAS] Key :password value '<suppressed>'
added to connectionProperties
[FINE] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.connector.DBConnector
setConnectionProperties - [DAAS] Key :user value 'domain\username' added
to connectionProperties
[FINEST] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.connector.DBConnector
getConnectionProperties - [DAAS] accessor call to connectionProperties
[FINE] 2018-08-22 08:31:00
com.netiq.daas.nativejdbcservice.connector.DBConnector
establishDBConnection - [DAAS] Caught SQLException: Login failed for
user 'domain\username'.
ClientConnectionId:00d9acdf-139d-4a9f-b8b0-baf0a0ad7d27
[FINE] 2018-08-22 08:31:00
com.netiq.iac.persistence.dcs.dce.daas.DaaSService testConnection -
[IG-SERVER] DaaS Service Test response code: 486


So bad login. Not a connection (firewall, etc) style problem.

This is really what I was asking about, thanks alekz!

Now I can see what is happening and get more details under the covers,
which is what I really need in order to troubleshoot!

Usefulness of a new log level revealed!

0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector

On 8/22/2018 9:33 AM, Geoffrey Carman wrote:
> On 8/22/2018 7:08 AM, Geoffrey Carman wrote:
>>>> [FINE] 2018-08-21 12:20:20
>>>> com.netiq.iac.persistence.service.cum.DataCollectionService
>>>> testConnection - [IG-SERVER] Encountered unexpected error:
>>>> DAAS_ERROR: 486 : Target Connection failure.
>>>> com.netiq.common.i18n.LocalizedException: Encountered unexpected
>>>> error: DAAS_ERROR: 486 : Target Connection failure.
>>>>
>>>>
>>>> Do we have access to a list of DaaS error codes?
>>>>
>>>> DaaS is Directory As a Service I would guess. There is a daas.war...
>>>> Guess go look and see what is in that expanded WAR file inside the
>>>> tomcat\webapps folder.
>>> You can edit daas-logging.xml in the tomcat/conf folder and restart
>>> Tomcat after changing INFO to TRACE.

>>
>> An excellent point! I forgot about that!  Two logging classes offered,
>> but parents...
>>
>> com.microfocus.daas
>> com.netiq.daas
>>
>> That is the hint I was looking for, thanks Alekz!  I should have
>> thought of that on my own.

>
> And we see with this logging enabled:
>
> [FINE] 2018-08-22 08:31:00 com.netiq.daas.daaservice.ServiceProviderMap
> clean - [DAAS] Collection cleaner running...
> [FINE] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.ConnectorFactory createConnector -
> [DAAS] Creating Microsoft SQLServer Specific Connector
> [FINE] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> setDriverClassName - [DAAS] Driver Class Name
> com.microsoft.sqlserver.jdbc.SQLServerDriver
> [FINE] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> setConnectionProperties - [DAAS] setting connectionProperties
> [FINE] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> setConnectionProperties - [DAAS] Key :databaseName value 'Test' added to
> connectionProperties
> [FINE] 2018-08-22 08:31:00 com.netiq.daas.common.SrvInstance <init> -
> [DAAS] New service instance.  TTL: 60
> [FINE] 2018-08-22 08:31:00 com.netiq.daas.common.SrvInstance
> resetTimeout - [DAAS] Reset timeout for service instance to TTL: 60
> [FINE] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> setConnectionProperties - [DAAS] setting connectionProperties
> [FINE] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> setConnectionProperties - [DAAS] Key :password value '<suppressed>'
> added to connectionProperties
> [FINE] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> setConnectionProperties - [DAAS] Key :user value 'domain\username' added
> to connectionProperties
> [FINEST] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> getConnectionProperties - [DAAS] accessor call to connectionProperties
> [FINE] 2018-08-22 08:31:00
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> establishDBConnection - [DAAS] Caught SQLException: Login failed for
> user 'domain\username'.
> ClientConnectionId:00d9acdf-139d-4a9f-b8b0-baf0a0ad7d27
> [FINE] 2018-08-22 08:31:00
> com.netiq.iac.persistence.dcs.dce.daas.DaaSService testConnection -
> [IG-SERVER] DaaS Service Test response code: 486
>
>
> So bad login.  Not a connection (firewall, etc) style problem.
>
> This is really what I was asking about, thanks alekz!
>
> Now I can see what is happening and get more details under the covers,
> which is what I really need in order to troubleshoot!
>
> Usefulness of a new log level revealed!


To follow up, I ran into two more errors that fall out of 486 with
additional logging:

[FINE] 2019-04-04 14:54:30
com.netiq.daas.nativejdbcservice.connector.DBConnector
establishDBConnection - [DAAS] Class resource to connect to the
underlying database not found: net.sourceforge.jtds.jdbc.Driver

Forgot to copy the JAR to the server. oopsey.

FINE] 2019-04-04 15:05:39
com.netiq.daas.nativejdbcservice.connector.DBConnector
establishDBConnection - [DAAS] Caught SQLException: Login failed. The
login is from an untrusted domain and cannot be used with
Windows authentication.

Poorly setup Auth.



0 Likes
Micro Focus Expert
Micro Focus Expert

Re: DAAS Error 486 when testing a JDBC Collector

On 4/4/19 4:36 PM, Geoffrey Carman wrote:
> On 8/22/2018 9:33 AM, Geoffrey Carman wrote:
>> On 8/22/2018 7:08 AM, Geoffrey Carman wrote:
>>>>> [FINE] 2018-08-21 12:20:20
>>>>> com.netiq.iac.persistence.service.cum.DataCollectionService
>>>>> testConnection - [IG-SERVER] Encountered unexpected error:
>>>>> DAAS_ERROR: 486 : Target Connection failure.
>>>>> com.netiq.common.i18n.LocalizedException: Encountered unexpected
>>>>> error: DAAS_ERROR: 486 : Target Connection failure.
>>>>>
>>>>>
>>>>> Do we have access to a list of DaaS error codes?
>>>>>
>>>>> DaaS is Directory As a Service I would guess. There is a
>>>>> daas.war... Guess go look and see what is in that expanded WAR file
>>>>> inside the tomcat\webapps folder.
>>>> You can edit daas-logging.xml in the tomcat/conf folder and restart
>>>> Tomcat after changing INFO to TRACE.
>>>
>>> An excellent point! I forgot about that!  Two logging classes
>>> offered, but parents...
>>>
>>> com.microfocus.daas
>>> com.netiq.daas
>>>
>>> That is the hint I was looking for, thanks Alekz!  I should have
>>> thought of that on my own.

>>
>> And we see with this logging enabled:
>>
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.daaservice.ServiceProviderMap clean - [DAAS] Collection
>> cleaner running...
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.ConnectorFactory createConnector -
>> [DAAS] Creating Microsoft SQLServer Specific Connector
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> setDriverClassName - [DAAS] Driver Class Name
>> com.microsoft.sqlserver.jdbc.SQLServerDriver
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> setConnectionProperties - [DAAS] setting connectionProperties
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> setConnectionProperties - [DAAS] Key :databaseName value 'Test' added
>> to connectionProperties
>> [FINE] 2018-08-22 08:31:00 com.netiq.daas.common.SrvInstance <init> -
>> [DAAS] New service instance.  TTL: 60
>> [FINE] 2018-08-22 08:31:00 com.netiq.daas.common.SrvInstance
>> resetTimeout - [DAAS] Reset timeout for service instance to TTL: 60
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> setConnectionProperties - [DAAS] setting connectionProperties
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> setConnectionProperties - [DAAS] Key :password value '<suppressed>'
>> added to connectionProperties
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> setConnectionProperties - [DAAS] Key :user value 'domain\username'
>> added to connectionProperties
>> [FINEST] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> getConnectionProperties - [DAAS] accessor call to connectionProperties
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> establishDBConnection - [DAAS] Caught SQLException: Login failed for
>> user 'domain\username'.
>> ClientConnectionId:00d9acdf-139d-4a9f-b8b0-baf0a0ad7d27
>> [FINE] 2018-08-22 08:31:00
>> com.netiq.iac.persistence.dcs.dce.daas.DaaSService testConnection -
>> [IG-SERVER] DaaS Service Test response code: 486
>>
>>
>> So bad login.  Not a connection (firewall, etc) style problem.
>>
>> This is really what I was asking about, thanks alekz!
>>
>> Now I can see what is happening and get more details under the covers,
>> which is what I really need in order to troubleshoot!
>>
>> Usefulness of a new log level revealed!

>
> To follow up, I ran into two more errors that fall out of 486 with
> additional logging:
>
> [FINE] 2019-04-04 14:54:30
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> establishDBConnection - [DAAS] Class resource to connect to the
> underlying database not found: net.sourceforge.jtds.jdbc.Driver
>
> Forgot to copy the JAR to the server. oopsey.
>
> FINE] 2019-04-04 15:05:39
> com.netiq.daas.nativejdbcservice.connector.DBConnector
> establishDBConnection - [DAAS] Caught SQLException: Login failed. The
> login is from an untrusted domain and cannot be used with
> Windows authentication.
>
> Poorly setup Auth.
>
>
>

Greetings,
A 489 is the typical error message that will be returne to the
client from a a REST call. To see the additional details one has to
look in the logs.

--
Sincerely,
Steven Williams
Principal Enterprise Architect
Micro Focus
0 Likes
Knowledge Partner
Knowledge Partner

Re: DAAS Error 486 when testing a JDBC Collector

On 4/22/2019 8:26 PM, Steven Williams wrote:
> On 4/4/19 4:36 PM, Geoffrey Carman wrote:
>> On 8/22/2018 9:33 AM, Geoffrey Carman wrote:
>>> On 8/22/2018 7:08 AM, Geoffrey Carman wrote:
>>>>>> [FINE] 2018-08-21 12:20:20
>>>>>> com.netiq.iac.persistence.service.cum.DataCollectionService
>>>>>> testConnection - [IG-SERVER] Encountered unexpected error:
>>>>>> DAAS_ERROR: 486 : Target Connection failure.
>>>>>> com.netiq.common.i18n.LocalizedException: Encountered unexpected
>>>>>> error: DAAS_ERROR: 486 : Target Connection failure.
>>>>>>
>>>>>>
>>>>>> Do we have access to a list of DaaS error codes?
>>>>>>
>>>>>> DaaS is Directory As a Service I would guess. There is a
>>>>>> daas.war... Guess go look and see what is in that expanded WAR
>>>>>> file inside the tomcat\webapps folder.
>>>>> You can edit daas-logging.xml in the tomcat/conf folder and restart
>>>>> Tomcat after changing INFO to TRACE.
>>>>
>>>> An excellent point! I forgot about that!  Two logging classes
>>>> offered, but parents...
>>>>
>>>> com.microfocus.daas
>>>> com.netiq.daas
>>>>
>>>> That is the hint I was looking for, thanks Alekz!  I should have
>>>> thought of that on my own.
>>>
>>> And we see with this logging enabled:
>>>
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.daaservice.ServiceProviderMap clean - [DAAS]
>>> Collection cleaner running...
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.ConnectorFactory createConnector -
>>> [DAAS] Creating Microsoft SQLServer Specific Connector
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>>> setDriverClassName - [DAAS] Driver Class Name
>>> com.microsoft.sqlserver.jdbc.SQLServerDriver
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>>> setConnectionProperties - [DAAS] setting connectionProperties
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>>> setConnectionProperties - [DAAS] Key :databaseName value 'Test' added
>>> to connectionProperties
>>> [FINE] 2018-08-22 08:31:00 com.netiq.daas.common.SrvInstance <init> -
>>> [DAAS] New service instance.  TTL: 60
>>> [FINE] 2018-08-22 08:31:00 com.netiq.daas.common.SrvInstance
>>> resetTimeout - [DAAS] Reset timeout for service instance to TTL: 60
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>>> setConnectionProperties - [DAAS] setting connectionProperties
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>>> setConnectionProperties - [DAAS] Key :password value '<suppressed>'
>>> added to connectionProperties
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>>> setConnectionProperties - [DAAS] Key :user value 'domain\username'
>>> added to connectionProperties
>>> [FINEST] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>>> getConnectionProperties - [DAAS] accessor call to connectionProperties
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>>> establishDBConnection - [DAAS] Caught SQLException: Login failed for
>>> user 'domain\username'.
>>> ClientConnectionId:00d9acdf-139d-4a9f-b8b0-baf0a0ad7d27
>>> [FINE] 2018-08-22 08:31:00
>>> com.netiq.iac.persistence.dcs.dce.daas.DaaSService testConnection -
>>> [IG-SERVER] DaaS Service Test response code: 486
>>>
>>>
>>> So bad login.  Not a connection (firewall, etc) style problem.
>>>
>>> This is really what I was asking about, thanks alekz!
>>>
>>> Now I can see what is happening and get more details under the
>>> covers, which is what I really need in order to troubleshoot!
>>>
>>> Usefulness of a new log level revealed!

>>
>> To follow up, I ran into two more errors that fall out of 486 with
>> additional logging:
>>
>> [FINE] 2019-04-04 14:54:30
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> establishDBConnection - [DAAS] Class resource to connect to the
>> underlying database not found: net.sourceforge.jtds.jdbc.Driver
>>
>> Forgot to copy the JAR to the server. oopsey.
>>
>> FINE] 2019-04-04 15:05:39
>> com.netiq.daas.nativejdbcservice.connector.DBConnector
>> establishDBConnection - [DAAS] Caught SQLException: Login failed. The
>> login is from an untrusted domain and cannot be used with
>> Windows authentication.
>>
>> Poorly setup Auth.
>>
>>
>>

> Greetings,
>    A 489 is the typical error message that will be returne to the
> client from a a REST call.  To see the additional details one has to
> look in the logs.


But if you do not enable higher logging for daas classes, the logs do
not offer any actual value.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.