Jan 10, 2023
09:18 AM
1 Kudo
Yes, I also set the Beacon settings to not upgrade automatically; I will handle that myself after the application server is upgraded. --Mark
... View more
Jan 09, 2023
01:44 PM
Hi all ... The time zone on my FNMS and Inventory Beacons is US Eastern. The time zone on my database server is UTC. Is this OK or must the database server also be in the US Eastern time zone? --Mark
... View more
Labels
- Labels:
-
Installation & Configuration
Jan 09, 2023
01:41 PM
1 Kudo
Hi all ... The Upgrade Guide goes into great detail regarding what should be done to upgrade the FNMS server itself. It doesn't go too deeply regarding how the existing Inventory Beacons should be treated. What I mean by this is - you have to make a decision regarding how you want interrupted inventory collection handled. You can leave the inventory beacons up which will accumulate inventory being uploaded from agents, or you can stop the inventory beacons to prevent this accumulation, and keep the inventory at the agent until you bring the Inventory Beacons back up. What is the "best practice" for this scenario? In my case, I am collecting inventory daily. If I leave the Inventory Beacons up during the FNMS upgrade, they'll accumulate a significant number of inventory files. When I wrap up the FNMS upgrade, these files will eventually be uploaded to FNMS and disappear from the Inventory Beacons. The FNMS upgrade itself takes several hours; a few hours to copy/restore the databases and a few hours to upgrade the databases (the Compliance database alone took about 3 hours to backup/restore and just over 2 hours to upgrade). So by the time the FNMS upgrade is done, most of the accumulated inventory could be considered "stale" (a day old) so there really wouldn't be a need to upload it, since entirely new inventory will be generated and uploaded the following day. Based on this, I'm inclined to stop the inventory beacons as part of my upgrade to negate the need for "catch-up work". I'd just skip inventory collection on the day of the upgrade. Is there something I am overlooking whereby I should not stop the beacons? --Mark
... View more
Labels
- Labels:
-
beacon
-
Installation & Configuration
Jan 04, 2023
04:31 PM
3 Kudos
I have seen, in the past, where an "improperly" set SQL Server Compatibility level could cause the Import / Reconciliation process to run long. For SQL Server 2019, the recommendation for this setting is "SQL Server 2019 (150)". Are your databases set to that compatibility level? (I have no experience with the setting you've described.) --Mark
... View more
Dec 20, 2022
02:10 PM
Did you recently create a business adapter that might have some issue? Other users in this forum who had the same error you did said that deleting a recently created business adapter resolved their issue. https://community.flexera.com/t5/FlexNet-Manager-Forum/Root-element-is-missing-error/td-p/127550 --Mark
... View more
Dec 20, 2022
01:57 PM
1 Kudo
What about a query against the InventoryReport table in the FNMSInventory database: --Show when computer(s) last reported their inventory select comp.computerCN, rept.SWDate, rept.HWDate, rept.FilesDate from FNMSInventory.dbo.Computer comp, FNMSInventory.dbo.InventoryReport rept where comp.ComputerID = rept.ComputerID and Cast(rept.SWDate as Date) = '2022-12-17' order by SWDate DESC The InventoryReport table contains a record of every user and computer that has reported hardware or software inventory through an agent. It details the date and time when the hardware or software tracking was performed. You could modify the above query to look for a particular date (or computer) and if one of those date columns is older than a certain date , you could consider it stale. --Mark
... View more
Dec 15, 2022
04:51 PM
I recently ran the Compliance database upgrade script (going from FNMS 2019R1 to 2022R1) and noticed that the migration script ended with the following statement: Full-text indexes not created because the full-text feature of SQL is not installed Does this imply that I should install the full-text feature, or is that simply informational? --Mark
... View more
Dec 15, 2022
04:36 PM
2 Kudos
Hi all ... I am going through the process of upgrading my FNMS environment from FNMS 2019R1 to 2022R1. I'm also taking this time to migrate onto faster hardware and from being based on Win2012R2 to Windows Server 2019. I am also migrating the database from SQL Server 2016 to SQL Server 2019. So the first step was to set up SQL Server 2019, apply CU 16 and then perform the additional setup Flexera requires (enable CLR, turn off six Intelligent Query Optimizer components, etc.). Next, I backed up and restored the FNMS databases from my production SQL Server 2016 server to the new one. Then, I copied over the database migration ZIP file, expanded it and started running the migration utilities. [Generally, this is all described in the Upgrade Guide to FNMS 2022 R1, pages 38 to 47.] I had no issues upgrading the Inventory Database. I did have an issue with the Compliance database: Running cm-migr1300-ComplianceSchema.sql...100%
Running cm-migr1300-CompliancePreCLRInstall.sql...50%
There was an error while attempting to run 'cm-migr1300-CompliancePreCLRInstall.sql'.
An error occurred in the Microsoft .NET Framework while trying to load assembly id 65538. The server may be running out of resources, or the assembly may not be trusted. Run the query again, or check documentation to see how to solve the assembly trust issues. For more information about this error:
System.IO.FileLoadException: Could not load file or assembly 'sqlproceduresclr, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An error relating to security occurred. (Exception from HRESULT: 0x8013150A)
System.IO.FileLoadException:
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
Others have had this same error as well. The entry I pointed to above listed two workarounds for this issue. (1) One solution was to run the below T-SQL commands, then run the Compliance upgrade utility, then changing TRUSTWORTHY to OFF and rerunning the commands: ALTER DATABASE [FNMSCompliance] SET TRUSTWORTHY ON GO USE [FNMSCompliance] GO EXEC sp_changedbowner 'sa' GO (2) The other solution implied that you could get the CLR certificate from a previous release, apply it, run the Compliance upgrade until it fails, remove the older certificate, then import the recent one and rerun the upgrade until it finishes. The second solution seemed like a lot of extra work, so I tried the first solution (TRUSTWORTHY set to ON while the upgrade runs, then set it OFF) and that worked for me. The database was upgraded successfully. However, I'm a little concerned I had to perform this workaround since it isn't officially documented in the upgrade guide. Are there any potential issues that could occur "down the road" because of how this was accomplished? I ask because this poster had a similar issue trying to run the config.ps1 command and stated "I did try to set Trustworthy as "True" during the Config.ps1 step and while that allowed the script to complete successfully, the application gave redbox errors on nearly every page after setting Trustworthy back to 'False'. " Granted, the cause of this poster's issue could have been different, but I obviously don't want to install FNMS later on and get redbox errors that tie back to this workaround. And if this is indeed the proper method of performing a database upgrade across several releases, shouldn't the upgrade guide be modified to reflect this as part of its procedures? --Mark
... View more
Labels
- Labels:
-
database
-
Installation & Configuration
Dec 15, 2022
11:05 AM
1 Kudo
@ChrisG , your guess was good. About 38,000 devices. --Mark
... View more
Dec 12, 2022
08:03 AM
2 Kudos
Hi all ... My reconciliation process that ran last night (Sunday 12/11) was back to normal. Total time was about 6 1/4 hours and the double-wildcard step ran in 54 minutes: 2022-12-12 04:57:36,288 [INFO ] WriteFileEvidence - Match double ended wildcards 2022-12-12 04:57:36,288 [INFO ] Writer step 'WriteFileEvidence - Match double ended wildcards' with non-default execution path (Fallback) meets condition TestingOrFallback. 2022-12-12 05:52:21,608 [INFO ] Matched 40923 records to existing File Evidence with start and end wildcards 2022-12-12 05:52:21,608 [INFO ] Successfully processed in 54 minutes, 45 seconds (Is 54 minutes a decent time to match on 40,923 records?) --Mark
... View more
Dec 09, 2022
10:23 AM
Thanks for the documentation link. Very helpful to me in understanding the setup. So it appears there's three things required to make this work: Installing the agent on the VDI template (or "golden image"). This was done with the SCCM push during my agent deployment. Installing the Citrix Remote PowerShell SDK onto a beacon. (not done yet) Configuring a connection in the FlexNet Beacon UI to Citrix. (not done yet) At the moment, only #1 has been done. Is it OK to leave this "as is" (inventory agent running) or must it be stopped until I set up the inventory beacon connection? My assumption is, in this state, I'll just get inventory from the VDI template. --Mark
... View more
Dec 08, 2022
11:55 AM
Hi all ... Before my laptop received the Flexnet Inventory Agent, its inventory was passed to FNMS using an SCCM Inventory Adapter. FNMS listed the "inventory device type" as Computer. Now that my laptop has the Inventory Agent on it (version 2021 R1), the "inventory device type" was changed to "VM Host". I've noticed this same change for many other laptops in my organization. Is there something in the agent's NDI file that triggered this change by FNMS? My laptop is a HP ProBook 640 G5, if that helps. --Mark
... View more
Labels
- Labels:
-
agent
-
Inventory Gathering & Data
Dec 08, 2022
11:31 AM
Hi all ... In my recent rollout of the Flexnet Inventory Agent for Windows (third-party deployment push of the 2021 R1 agent through SCCM), the agent was automatically installed on a Windows image in a non-persistent Citrix VDI environment. I know little about Citrix VDI. The question asked of me was "how does the agent work in a non-persistent VDI environment and what its impact might be?" I've read some prior postings about setting up Discovery & Inventory rules for collecting this inventory. None of these are done at this time. Could the experts kindly weigh in on my question or point me to documentation which answers it? If my question needs clarifying data (for example, "Windows image in a Citrix VDI environment" is too general), please let me know what is needed. Thanks for your help. --Mark
... View more
Dec 08, 2022
10:06 AM
The fact that you are running a different release of the FNMS server than I am, and that my FNMS server has the same issue as you, tells me that this is likely the result of "some change". I see further down that the current thought is Tibco wildcard entries in the ARL that are soon to be backed out. Hopefully that is the source of the issue.
... View more
Dec 08, 2022
10:03 AM
Thanks for the attention this issue is getting. In my case, the issue started with the 12/4 reconciliation. My ARL was updated on 12/3 (and is done weekly on Saturdays). (I originally thought it had something to do with my agent rollout but I now see that was just a big coincidence.) Edit: I am using FNMS 2019 R1 on prem (server upgrade is planned in a few weeks). --Mark
... View more
Latest posts by mfeinman
Subject | Views | Posted |
---|---|---|
133 | Jan 10, 2023 09:18 AM | |
100 | Jan 09, 2023 01:44 PM | |
178 | Jan 09, 2023 01:41 PM | |
219 | Jan 04, 2023 04:31 PM | |
319 | Dec 20, 2022 02:10 PM | |
128 | Dec 20, 2022 01:57 PM | |
169 | Dec 15, 2022 04:51 PM | |
223 | Dec 15, 2022 04:36 PM | |
217 | Dec 15, 2022 11:05 AM | |
289 | Dec 12, 2022 08:03 AM |
Activity Feed
- Got a Kudo for Re: FNMS on SQL 2019 and Legacy Cardinality Estimator (CE). Jan 16, 2023 01:28 AM
- Got a Kudo for Re: When Upgrading FNMS On-Prem, Do You Also Stop Your Inventory Beacons or Do You Leave Them Running?. Jan 11, 2023 02:02 AM
- Posted Re: When Upgrading FNMS On-Prem, Do You Also Stop Your Inventory Beacons or Do You Leave Them Running? on FlexNet Manager Forum. Jan 10, 2023 09:18 AM
- Kudoed Re: When Upgrading FNMS On-Prem, Do You Also Stop Your Inventory Beacons or Do You Leave Them Running? for ChrisG. Jan 10, 2023 09:17 AM
- Got a Kudo for When Upgrading FNMS On-Prem, Do You Also Stop Your Inventory Beacons or Do You Leave Them Running?. Jan 10, 2023 01:11 AM
- Kudoed Re: Time Zone on Database Server: UTC; On FNMS and Beacons: US Eastern. Is This OK? for ChrisG. Jan 09, 2023 04:40 PM
- Posted Time Zone on Database Server: UTC; On FNMS and Beacons: US Eastern. Is This OK? on FlexNet Manager Forum. Jan 09, 2023 01:44 PM
- Posted When Upgrading FNMS On-Prem, Do You Also Stop Your Inventory Beacons or Do You Leave Them Running? on FlexNet Manager Forum. Jan 09, 2023 01:41 PM
- Kudoed Re: FNMS on SQL 2019 and Legacy Cardinality Estimator (CE) for ChrisG. Jan 06, 2023 03:20 PM
- Kudoed Re: FNMS on SQL 2019 and Legacy Cardinality Estimator (CE) for steffen. Jan 06, 2023 03:20 PM
- Got a Kudo for Re: FNMS on SQL 2019 and Legacy Cardinality Estimator (CE). Jan 05, 2023 12:14 PM
- Got a Kudo for Re: FNMS on SQL 2019 and Legacy Cardinality Estimator (CE). Jan 04, 2023 10:56 PM
- Kudoed Re: Automating the Status of Applications in FNM On-Prem for dbeckner. Jan 04, 2023 04:36 PM
- Kudoed Re: Automating the Status of Applications in FNM On-Prem for ChrisG. Jan 04, 2023 04:36 PM
- Posted Re: FNMS on SQL 2019 and Legacy Cardinality Estimator (CE) on FlexNet Manager Forum. Jan 04, 2023 04:31 PM
- Got a Kudo for Re: FlexNet Agent Alerts. Dec 20, 2022 07:25 PM
- Kudoed Re: Compliance Database Upgrade Error (Could Not Load Assembly "sqlproceduresclr") Going From FNMS 2019R1 to 2022R1. I Resolved It But Have A Question. for darren_haehnel. Dec 20, 2022 02:13 PM
- Posted Re: Error while opening FlexNet Beacon on FlexNet Manager Forum. Dec 20, 2022 02:10 PM
- Posted Re: FlexNet Agent Alerts on FlexNet Manager Forum. Dec 20, 2022 01:57 PM
- Kudoed Automating the Status of Applications in FNM On-Prem for dbeckner. Dec 16, 2022 02:53 PM