RMA and File Folder Size.

StevenE · Post by **StevenE** » Fri Jan 13, 2006 3:54 pm

I setup a test to monitor a particular file and it works fine from HM, when I change the test to run from the RMA client I get an error.

RDI ( File Size ) Unknown RMA: 301 - Folder/File doesn`t exist Folder size

I checked the machine running the agent and it does have access to that file.

HM 5.71

StevenE

KS-Soft · Post by **KS-Soft** » Fri Jan 13, 2006 4:07 pm

RMA is started as service? Have you tried to start agent in application mode?
Probably account that is used to start agent does not have rights to access folder?

HM 5.71

More interesting agent version. 3.15?

Regards
Alex

StevenE · Post by **StevenE** » Mon Jan 16, 2006 9:56 am

Okay,

As an Application the test works fine, as a service the test fails.

RMA 3.15c

Steven

KS-Soft · Post by **KS-Soft** » Mon Jan 16, 2006 10:14 am

It means account that is used to start agent does not have rights to access folder.

Regards
Alex

StevenE · Post by **StevenE** » Mon Jan 16, 2006 10:45 am

Okay,

Giving the RMA Agent service an administrator logon account, resolved the problem.

Sort Of.....

Shouldn't the File/Folder Test have the ability to specify a username and password like the Space Free-Test ?

StevenE

KS-Soft · Post by **KS-Soft** » Mon Jan 16, 2006 3:00 pm

1) If you start service under local system account, user name and password will not help. Local system account cannot use network functions
2) If you have to use different credentials for this test, use Connection Manager: http://www.ks-soft.net/hostmon.eng/mfra ... htm#conmgr

Regards
Alex

StevenE · Post by **StevenE** » Mon Jan 16, 2006 3:47 pm

Wow,

I missed that in the manual, It seems to work fine.

Does it work with ODBC through RMA client also ?

Thanks
StevenE

KS-Soft · Post by **KS-Soft** » Mon Jan 16, 2006 4:05 pm

ODBC test has its own settings, it doesn't need Connection Manager

Regards
Alex

StevenE · Post by **StevenE** » Tue Jan 17, 2006 8:28 am

I thought maybe I could specify all the usernames and passwords in connections manager instead of each test.

Thanks for the Help and Info.

StevenE

StevenE · Post by **StevenE** » Fri Jan 27, 2006 3:58 pm

The problem I ran into is,

When using the odbc test through RMA agent I had to give the RMA agent service a administrator account to use to access the Microsoft Access Databases on remote machines.

Ex.

ODBC test to \\pc$\c$\app\app.mdb.

Through RMA this test fails. Unable to access the file.

Giving the RMA Service a administrator account username and password the test passes.

I have tried to specify the same administrator account and password withing the test itself and it does not work.

StevenE

KS-Soft · Post by **KS-Soft** » Sat Jan 28, 2006 11:22 am

Why you are writing about ODBC problem using "RMA and File Folder" topic? It looks like completely different problem.

Anyway, if you start agent (or any other service) under local system account, it simply does not have rights to use Windows network functions. You may specify user name and password that RMA passes to Windows API / ODBC driver but it cannot help because application does not have permissions.
So, use admins account. Nothing wrong with it.

Regards
Alex

johnm · Post by **johnm** » Mon Apr 17, 2006 9:39 am

Alex, I too am having a similar problem. The agent is installed on a Win2K Server which logs into a domain as domain administrator. The agent service is configured to logon using the same domain administrator. However, I have a file/folder size test which fails with an RMA 301 error if I run the agent as a service. The test succeeds if I run the agent as an application. I am not currently using but have tried making an entry in Connection Manager in both cases - service and app, but it makes no difference, test still fails. The only way to correct the problem is to run as an app as I mentioned above.

I would really like to run it as a service so that it starts regardless if the console is logged on or not.

Any ideas?

KS-Soft · Post by **KS-Soft** » Mon Apr 17, 2006 11:17 am

Some permission issue... try local admin account

Regards
Alex