We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Cannot load data from an existing XBRL file (Requested security protocol is not supported

I’m getting the error when I’m attempting the following:
XbrlDocument document = new XbrlDocument(@“c:\temp” + @“mysamplefile.xml”);

Project is a .NET 5 core project / C#, using Aspose.Finance 22.5.0.


at System.Net.ServicePointManager.ValidateSecurityProtocol(SecurityProtocolType value)
at System.Net.ServicePointManager.set_SecurityProtocol(SecurityProtocolType value)
at Aspose.Finance.Xbrl.LocalCacheService.(String )
at .()
at .()
at .()
at .(XmlNode )
at .()
at Aspose.Finance.Xbrl.XbrlDocument.(Stream )
at Aspose.Finance.Xbrl.XbrlDocument…ctor(String fileName)


Could you please zip and attach XBRL document (XML file). We will check your issue soon.

sample.zip (2.8 KB)

Can you make it a private download?


Thanks for the sample file.

Please notice, I am able to reproduce the issue as you mentioned by using your sample document in a .NET 5.0 Core project. I found an exception “The requested security protocol is not supported” on loading the XBRL document. I have logged a ticket with an id “FINANCENET-168” for your issue. We will look into it soon.

Once we have an update on it, we will let you know.

Could you recommend a different a different .NET framework where this does work?


No, I would not recommend. Please spare us little time to evaluate your issue in details. Hopefully your issue would be figured out soon.

Additionally, I got the same when I try the following:
Aspose.Finance.Xbrl.XbrlDocument xbrlDocument = new Aspose.Finance.Xbrl.XbrlDocument();
var id = xbrlDocument.XbrlInstances.Add();
var contextInstance = xbrlDocument.XbrlInstances[id];
contextInstance.SchemaRefs.Add(“https://www.xbrl.org/2003/instance”, “xbrli”);


Your are right as I tested it as well. I have logged your findings with the existing ticket “FINANCENET-168” into our database. We will analyze your issue in details.

The issues you have found earlier (filed as FINANCENET-168) have been fixed in this update. This message was posted using Bugs notification tool by WilliamShen