Showing results for 
Show  only  | Search instead for 
Did you mean: 

The SQL process didn't constitute the Database Service despite Full Stack mode is use in the OneAgent in Database Machine

Normally I install Full-Stack One Agent in all tier (web tier, app tier, any other middle tier) but the db tier (db tier would be using cloud-infra).

So my understanding is that in this type of installation I've always use:

i) I able to see database service because the service in the app tier make a service call to the SQL

ii) I able to see the SQL process in the DB host, but the process wouldn't take me to service because it isn't in full-stack mode.

IF my above understanding is correct, now that I've enable the OneAgent in database host to be in full-stack, yet I still see the same thing (refer to the 2 diagram below):

Anybody know why?


DynaMight Pro
DynaMight Pro

how long is agent on db server running in fullstack mode ?

Alanata a.s.

I don't remember the exact date, but it is definitely more than 7 days ago

DynaMight Pro
DynaMight Pro

maybe it's just because on db host you can see only db process group "MSSQL12.PSQNS02" which cannot be connected with db service named "AET_Office"..

what are members of process group named "MSSQL12.PSQNS02" ?

Alanata a.s.

Got the reply from support team, it MIGHT be because of database framework not supported

I just compared two SQL Clusters in my environment. One that is working and the other that isn't. The frameworks are the same.


I'm experiencing the exact same issue. Has there been any solution? @Wai Keat C.

Nope. The last I heard from Support Team is ask me to check the framework.

I asked customer to ask their vendor what database framework they are using. The POC exercise already ended but still their vendor couldn't answer the question......

Featured Posts