- CheckMates
- :
- Products
- :
- Quantum
- :
- SmartMove
- :
- Smart Move Error: During converting Fortinet OS t...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Smart Move Error: During converting Fortinet OS to Checkpoint
Hi,
I am trying to convert Fortinet OS to Checkpoint GAIA R80.20 using SmartMove.
But getting bellow error message during this process:
Could not convert configuration file.
Message: Value cannot be null.
Parameter name: key
Module: mscorlib
Class: Directory'2
Method: FindEntry
Error Message
Please suggest.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would rather open a SR# with TAC instead...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
As of now opening a TAC case is not able for me.
I am testing it in LAB Environment.
So please suggest what may be the cause of below error:
could not convert configuration file.
Message: Value cannot be null.
Parameter name: key
Module: mscorlib
Class: Dictionary'2
method: FindEntry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Regards,
CSR
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am also getting same error when converting from fortigate to checkpoint.
Is there any resolution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same problem here. Did anyone get a solution to this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was facing the same issue. I was working with global configuration file of Fortigate which includes all the VDOM. That file didn't work so I tried with configuration file of particular VDOM which worked. But it didn't work straight away. I had to delete dynamic routing configuration from the file which was there at the end of the configuration. Try deleting small portions of configuration from the file and check if it works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
