CF2021 Administrator Setting Summary Page Error

[--jojo--]

I've tried multiple installations now - completely new. After the configuration is complete, and I navigate to the Administrator > Settings Summary page, I get the following error:

The getMachineUUID method was not found.Either there are no methods with the specified method name and argument types or the getMachineUUID method is overloaded with argument types that ColdFusion cannot decipher reliably. ColdFusion found 0 methods that match the provided arguments. If this is a Java object and you verified that the method exists, use the javacast function to reduce ambiguity. The specific sequence of files included or processed is: C:\ColdFusion2021\cfusion\wwwroot\CFIDE\administrator\reports\index.cfm, line: 191

What gives????

[BKBK]

GetMachineUUID() is most likely a Java call that ColdFusion makes internally when gathering properties of the Operating System. Perhaps your Operating System was busy with something else when you installed ColdFusion. Another possibility is that you installed ColdFusion when there were still remnants of a previous installation attempt on the server. 

Suggestion:

1. Uninstall ColdFusion 2021;
2. Restart the server;
3. Search and remove any remnants of the ColdFusion 2021 installation;
4. Update the server if necessary;
5.  Install ColdFusion 2021.

[--jojo--]

@BKBK It's an AMI from the AWS marketplace. I've tried both a community version and a marketplace AMI, both resulted in the same problem. 

[Priyank Shrivastava.]

Hi,

As per the above comment, I assume you are using ColdFusion AMI which is available in Market Place. Could you please let me know what configuration changes are you making which after which it is breaking the Setting Summary PDF.

Please share the steps. I will give it a try.

[--jojo--]

@Priyank Shrivastava. -- this is out of the box AMI install. The only things I install during the configuration process are S3, pdf, sql server, odbc - then as soon as the server is configured, without making any changes, I go to the Setting Summary and I get that error. 

This is the AMI - https://aws.amazon.com/marketplace/pp/prodview-ci675r6zeagle?sr=0-3&ref_=beagle&applicationId=AWS-EC...

[Charlie Arehart]

Jojo, it's great that Priyank has stepped in, and he may get you all set. But here's a thought for you both: I see said that you installed only a few modules, and that's a feature of CF2021, sure.

But I wonder if the error may go away if you just installed all modules.  I agree it would seem a bug that you should have to, and perhaps Priyank may even try this, but I offer it as a suggestion for you. 

[Charlie Arehart]

Jojo, I've never seen that error. And when I see such odd errors, I am inclined to blame a failed cf update. Had you applied any recently? Or are these AMIs as you got them? If the latter, what update is shown, if you can look at the system info page or the updates installed page? If you did do an update, look at the install log for that update (in the hf-updates folder's subfolder for the update): does it show a count of 0 fatalerrors? 

Finally, to your comment to bkbk, I've not heard of a "community" AMI. Can you be more specific? 

[--jojo--]

Thanks @Charlie Arehart - I didn't have to run any updates, the AWS Marketplace AMI is already on the latest (update 3). 

There's no direct link to the AMI, but this is listed under the Community AMIs in AWS

ColdFusion 2021 On Windows 1639774705-e4f2020f-65e7-4e97-87ac-93483674e810

ami-060ae5c3030544a38

ColdFusion 2021 On Windows 1639774705

[Charlie Arehart]

Since cf2021 does not (yet) come pre-installed with update 3, that would suggest that someone at coalesce had to do the update (or Adobe did it before giving the result as an Ami to coalesce). So I'd still recommend you check that update install log.

But I see Priyank has replied also and I will add a different thought as a reply there. Still, you may want to rule out what I suggest here, for his sake as much as yours. 🙂 

[Priyank Shrivastava.]

What if you revert someone these packages one by one and see which one is causing the problem? If I find out, I can talk to the team at Coalesce.

[BKBK]

What if you revert someone these packages one by one and see which one is causing the problem? 

By Priyank Shrivastava.

Hi @Priyank Shrivastava., given:

• getMachineUUID()

• C:\ColdFusion2021\cfusion\wwwroot\CFIDE\administrator\reports\index.cfm, line 191

couldn't the ColdFusion Team locate the source of the error?

[BKBK]

After the configuration is complete, and I navigate to the Administrator > Settings Summary page, I get the following error:

The getMachineUUID method was not found.Either there are no methods with the specified method name and argument types or the getMachineUUID method is overloaded with argument types that ColdFusion cannot decipher reliably. ColdFusion found 0 methods that match the provided arguments. If this is a Java object and you verified that the method exists, use the javacast function to reduce ambiguity. The specific sequence of files included or processed is: C:\ColdFusion2021\cfusion\wwwroot\CFIDE\administrator\reports\index.cfm, line: 191

By --jojo--

On second thoughts, this is ColdFusion's responsibility, not yours. What with

getMachineUUID

and

C:\ColdFusion2021\cfusion\wwwroot\CFIDE\administrator\reports\index.cfm

So I would call it a bug.

[Priyank Shrivastava.]

Hi All,

We are able to replicate the issue and currently working on it. Once we fix it, I will update the thread. 

[--jojo--]

Thanks, @Priyank Shrivastava. 

[BKBK]

We are able to replicate the issue and currently working on it. Once we fix it, I will update the thread. 

By Priyank Shrivastava.

Nice development. Thanks, @Priyank Shrivastava. .

[Priyank Shrivastava. · Accepted solution]

Hi All,

We have identified the issue and prepared the patch for this. We have shared the patch with the team and they will update the AMI. Once it is updated, I will update the thread. 

[--jojo--]

@Priyank Shrivastava. -- would that require us to reinstall from the AMI or is that patch going to be available via a standard patch?

[Priyank Shrivastava.]

Hi All,

I have shared the patch with @--jojo--  and he confirmed the fix. Thanks @--jojo-- @BKBK @Charlie Arehart 

[BKBK]

I have shared the patch with --jojo--  and he confirmed the fix. Thanks --jojo-- BKBK Charlie Arehart 

By Priyank Shrivastava.

Thanks, @Priyank Shrivastava. .

Exemplary support!

[Charlie Arehart]

Yep, great to see the quick turnaround. And while correcting things for new cf2021 AMI's is great to hear, will this patch be made available for those running one already, as Jojo was and it did work?

Would it be that they have to ask, or could you create a bug report and post it there? (Perhaps with a bit more about any characteristics that might impact the problem happening or not?)

Thanks. 

[Priyank Shrivastava.]

Hi Charlie,

It will be available in next update and we are fixing this in AMI. As of now, no one has reported this issue however in case anyone need the fix, they can reach out to us and we will provide that. 

I have logged an internal bug for this issue.

[Charlie Arehart]

Ok, thanks. But why an internal bug? Someone may go searching in tracker for a possible fix but won't find it.  And they may or may not find this discussion. 

Just trying to solve the problem more generally, with what seems a simple solution. 🙂 Is there something I'm not seeing? 

[kenji kishino]

I too am having trouble with this issue.
Could you please share the patch?

[Priyank Shrivastava.]

Hi @kenji kishino 

May I know the update level are you in currently?

[kenji kishino]

@Priyank Shrivastava. 

Thanks for your message.
The current update level is update 3.

Thanks,