Janet Chenery asked a question.
If a license doesn't have an associated agreement, what is a best practice approach for import? i.e. T&Cs, EULA,
Skip Feed
Correction Release: SharePoint scheduled report exports no longer fail due to duplicate file names
What was happening?
A scheduled report export to SharePoint could fail with a "Name already exists" error when a file with the same name already existed in the target location or when multiple users generated the same report simultaneously. In these situations, SharePoint rejected the upload and the report was not delivered.
What has been changed?
Every export now receives a unique file name. Export file names have been updated to include additional identifiers, helping prevent conflicts when files with the same name are generated or uploaded concurrently:
- Milliseconds in the timestamp
- A 6-character unique ID (GUID) suffix (Example : AdobeCC_20260930123000001_2e0d0c)
What this means for you?
- Scheduled exports should no longer fail due to duplicate file names.
- Reports scheduled for SharePoint delivery should arrive more reliably.
- Exported file names will look slightly different because they now include a more precise timestamp and a unique ID suffix.
Is any action required?
Existing schedules will continue to run without interruption, and the update is applied automatically. If downstream integrations, such as Power BI, depend on the exported files, review and update any file name references as needed to ensure those integrations continue to operate correctly.
Release Info:
Product: SAM on Snow Atlas(Report export to SharePoint)
Type: Correction
Release date: 21 September 2026
Expand Postshocko asked a question.
Report full computer name instead of HostnameWe are using Snow License Manager on-prem Version 26.3 Build 9732 with the snow inventory agent 7 insatalled on Windows 2016+ servers and Linux Servers. We noticed that the 'Computer Name' column in the inventory is reported as the HostName . For example if the computer DNS name is systemA.lab.net it's reported as systemA.
Q: How can we get it to show the full computer name including domain?
Expand Postshocko asked a question.
Domain Name Inventory InconsistenciesWe are using Snow License Manager on-prem Version 26.3 Build 9732 with the snow inventory agent 7 insatalled on Windows 2016+ servers and Linux Servers. We noticed that the domain name is reported as the domain ShortName (down-level domain name) on Windows whereas on Linux the FQDN of the domain is reported. For example if the domain is lab.net on Linux it's reported as lab.net but on windows as LAB.
Q: How can we get Windows to report the FQDN of the domain it's joined to?
Expand Postmkrautler@tampaairport.com asked a question.
Why does my DataExplorer backup give me an unhandled exception during Snow Inventory upgrade?I cannot run the Snow Inventory Data Explorer (a prompt from the Snow Inventory installer) to export all my computers from Snow (to back it all up prior to an upgrade) while I'm trying to upgrade Snow Inventory Server from v6 to v25.1.
When I run the installer it asks for the SQL db connections (which I think are correct because I can login to SQL from that machine as that account) but it gives me an unhandled exception error saying it invalid object name 'client' (see exception below) and then just crashes. I couldn't find any logs in Event Viewer nor any for DataExplorer under C:\Program Files\Snow Software\Logs\ directory.
I'm upgrading the following components versions below, is there any way to get this data backed up without having ot go through the DataExplorer backup process? Any assistance would be greatly appreciated, thanks in advance!
Inventory 6 -> 25.1
LicenseMgr 9 -> 26.1
Integration 6.3 -> 26.2
Unhandled Exception (truncated):
************** Exception Text **************
System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'Client'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData()
at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
at SnowSoftware.DB.DataFactory.ExecuteSPDataSet(String StoreProcName, String[] ParamNames, String[] ParamValues) in c:\Development\Snow Data Transfer\Source\DataFactory.cs:line 37
at SnowSoftware.SnowDataTransfer.TransferManager.GetComputerList(String connectionString, String siteName, String computerName) in c:\Development\Snow Data Transfer\Source\TransferManager.cs:line 43
at SnowSoftware.SnowDataTransfer.frmMain._btnTransfer_Click(Object sender, EventArgs e) in c:\Development\Snow Data Transfer\Source\frmMain.cs:line 218
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
ClientConnectionId:400a19c0-0677-44cc-a603-4c153db35a40
Error Number:208,State:1,Class:16
Expand PostPlain Text Snow-DataExplorer-Exception_09292026
ashwini.karigowda@valmetpartners.com asked a question.
SNOW Adobe downgrade versions license consumption, how to works in SNOW, Adobe CC is mandatory for thisRelease notification: Edit of multiple agreements (standard fields) in SAM on Snow Atlas
Release summary:
We are excited to introduce Edit of multiple agreements (standard fields) in SAM on Snow Atlas. This enhancement enables you to update multiple agreements in a single operation, directly from the Agreements list, eliminating repetitive manual updates and reducing reliance on APIs or technical support.
What’s included?
- Multi-editing capability: Select and update up to 1,000 agreements of the same type in one action.
- Standard field updates: Modify key agreement attributes across multiple records simultaneously.
- In-app experience: Perform all updates directly from the Agreements list without APIs, imports or external tools.
- Permission consistency: Uses existing edit permissions with no additional configuration required.
- Audit log support: Multi-edit updates are recorded in the audit log, providing visibility into changes made across agreements.
- For each agreement value or setting:
- Only changed values are updated.
- If the selected agreements share the same value, it appears in the edit view.
- If the selected agreements have different values before the change, you will see "Values differ" in the edit view.
Why this matters?
- Removes repetitive work: Eliminates the need to update agreements one by one.
- Saves significant time: Multi-editing that previously took time can now be completed in seconds.
- Improves data consistency: Apply changes across multiple agreements simultaneously, reducing the risk of errors.
- Reduces technical dependency: Enables users to perform multi-editing without relying on APIs, imports, or technical teams.
- Frees up time for strategic work: Allows teams to focus on higher-value activities such as compliance, optimization, and vendor management.
What’s next?
- Support for editing custom fields for agreements is currently in development and testing, with an EA release planned for early Q4.
- The improved performance and new backend architecture will also allow users to edit up to 10,000 agreements of the same type in a single action.
Release Info:
· Release date: September 24, 2026
· Product domain: SAM on Snow Atlas
· Release availability: General Availability (GA)
· Documentation: https://docs.flexera.com/snow-atlas/sam-core/sam-core-user-interface/agreements/manage-agreements
Expand Postjohmjosu asked a question.
Not able to logon to SMACC with administrator after installationFirsth time logon does not work. Can I create a new user in inventory and have that syncronised to splamanger database to get access?
End of Feed
8 Chatter Feed Items
