Need more  to go on to assist with this.

Have you checked that you have a zowe profile and the associated zowe schema in the same folder location? 
What else has changed in the time you have been using this?

Yes.  the schema is in the same location.   I upgraded the zmf explorer to the latest version.

The 2 files need to be in the .zowe folder.
Also, V2.0.5 is actually the most current version but that is an aside.. V2.0.5 has been out for quite some time. and no reported issues.
Any of your colleagues having the same problem?
 The error is itself coming out of zowe profile management modules.

You may want to provide the ZMF Explorer log file so I can take a look.

I didn't realize that I am using 2.0.5

community.microfocus.com/.../zmfExplorer.log

It would appear there is something not quite right in your profile. Please send the zowe.config.json. 
You could also try issuing a native zowe zmf command such as zowe zmf get ze  - (assuming you have the ZMF plugin for zowe cli also installed). 

{
"$schema": "./zowe.schema.json",
"profiles": {
"zosmf": {
"type": "zosmf",
"properties": {
"port": 999
},
"secure": []
},
"tso": {
"type": "tso",
"properties": {
"account": "",
"codePage": "1047",
"logonProcedure": "IZUFPROC"
},
"secure": []
},
"ssh": {
"type": "ssh",
"properties": {
"port": 99
},
"secure": []
},
"rse": {
"type": "rse",
"properties": {
"port": 9999,
"basePath": "rseapi",
"protocol": "https"
},
"secure": []
},
"zOpenDebug": {
"type": "zOpenDebug",
"properties": {
"dpsPort": 9999,
"dpsContextRoot": "api/v1",
"dpsSecured": true,
"uuid": "d6569caa-4294-4b4a-a9db-0c520bff59ea"
},
"secure": []
},
"base": {
"type": "base",
"properties": {
"host": "ibmmain.nml.com",
"rejectUnauthorized": true
},
"secure": [
"user",
"password"
]
},
"zmf_serzmfp": {
"type": "zmf",
"properties": {
"protocol": "http",
"host": "ibmmain.nml.com",
"port": 9999,
"basePath": "/zmfrestp",
"rejectUnauthorized": false
},
"secure": [
"user",
"password"
]
},
"zosmf_tst2": {
"type": "zosmf",
"properties": {
"host": "ibmmain.nml.com",
"port": 9999,
"rejectUnauthorized": false,
"certFile": "ibmzosmf/api/v1",
"basePath": "ibmzosmf/api/v1",
"protocol": "https",
"responseTimeout": 5
},
"secure": [
"user",
"password"
]
}
},
"autoStore": true
}

I was able to execute zowe zmf get

It appears that you have been running V2.0.5 since at least February as the log you provided showed it from that time. I assume it was running without any issues at that time.

Also there appears to have been a lot of changes since February. In February, you had 3 profiles specified - n,p and s and was pointing to one host. In June the profile appears to have changed and only p is now present and pointing to a different host.

As the error message is being returned from a zowe method please send in the imperative log from the same file location as where you provided the ZMF log file. 

I have asked the Broadcom folk who support zowe o shed any light on what that error message might mean. It does seem to point to a profile or schema related issue.

I took out the N and S environment because they were upgraded to version 8.3.0 plus the CMN ports are secured but the tomcat port is not yet secured.   P is version 8.2.6 and neither is port is yet secured.   I thought the multiple version and the secure/non-secure ports may be part of the issue.    In February all the environments were 8.2.6.

In the log I see this.

[2024/06/13 09:15:57.002] [ERROR] [CommandProcessor.js:315] Profile of type "zmf" does not exist within the loaded profiles for the command and it is marked as required.
[2024/06/13 09:15:57.010] [ERROR] [CommandYargs.js:148] Error in command zmf-environment
[2024/06/13 09:15:57.011] [ERROR] [CommandYargs.js:149] [

error: {
msg: 'Profile of type "zmf" does not exist within the loaded profiles for the command and it is marked as required.',
additionalDetails: 'This is an internal imperative error. Command preparation was attempting to extract option values from this profile.'

community.microfocus.com/.../8132.imperative.log

As I mentioned, I think this is the problem.  No zmf profile is being found where it is expected to be located. 

[2024/06/13 09:15:57.002] [ERROR] [CommandProcessor.js:315] Profile of type "zmf" does not exist within the loaded profiles for the command and it is marked as required.
[2024/06/13 09:15:57.010] [ERROR] [CommandYargs.js:148] Error in command zmf-environment
[2024/06/13 09:15:57.011] [ERROR] [CommandYargs.js:149] [

I have heard back from the zowe team at Broadcom and they suspect that the zowe.schema.json file is at fault.

You should review that file and if possible compare it with the same file from a colleague who is not experiencing the problem.

Thank you.

Did you make any progress with resolving this?

Yes.  I finally got it working.  I just have not had a chance to update you.  I had to make changes to the schema file to get it to work.  The ZMF profile need to be defined.

configurations",
"patternProperties": {
"^\\\\S*$": {
"type": "object",
"description": "Profile configuration object",
"properties": {
"type": {
"description": "Profile type",
"type": "string",
"enum": [
"zosmf",
"tso",
"ssh",
"zmf",
"base"
]

......

{
"if": {
"properties": {
"type": {
"const": "zmf"
}
}
},
"then": {
"properties": {
"properties": {
"type": "object",
"title": "Configuration profile for ChangeMan ZMF",
"description": "Configuration profile for ChangeMan ZMF",
"properties": {
"protocol": {
"type": "string",
"description": "The protocol used to connect to the ChangeMan ZMF Rest API server (http or https)",
"default": "http",
"enum": [
"http",
"https"
]
},
"host": {
"type": "string",
"description": "Host name of the ChangeMan ZMF REST API server"
},
"port": {
"type": "number",
"description": "Port number of the ChangeMan ZMF REST API server"
},
"user": {
"type": "string",
"description": "User name to authenticate to the ChangeMan ZMF REST API server"
},
"password": {
"type": "string",
"description": "Password to authenticate to the ChangeMan ZMF REST API server"
},
"basePath": {
"type": "string",
"description": "The base path used for connecting to the ChangeMan ZMF Rest API server",
"default": "/zmfrest"
},
"rejectUnauthorized": {
"type": "boolean",
"description": "Reject self-signed certificates",
"default": true
}
},
"required": []
},
"secure": {
"items": {
"enum": [
"user",
"password"
]
}
}
}
}
},

....

"properties": {
"zosmf": {
"description": "Default zosmf profile",
"type": "string"
},
"tso": {
"description": "Default tso profile",
"type": "string"
},
"ssh": {
"description": "Default ssh profile",
"type": "string"
},

"base": {
"description": "Default base profile",
"type": "string"
}

OK good.