Power Automate Copy file no longer works - Copy SharePoint Home.aspx to New SharePoint site

Anonymous
2024-09-19T10:30:35+00:00

Need help:

Power Automate Copy file not working since 18.9.2024 - copy SharePoint Home.aspx to New SharePoint site, error: Invalid number value. A number field contains invalid data. Please check the value and try again. CallStack -- at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx) at Microsoft.SharePoint.Library.SPRequest.SetGhostedFile(String setupPath, Byte setupPathVersion, Int32 iVersion, Guid& pguidListId, Guid& pguidDocId, Int32 lDoclibRowId, Int32 iAuthorId, String authorLogin, String serverRelativeUrl, String targetUrlWebRelative, Boolean isInDocLib, Boolean isMigration, Boolean isPublishing Object varProperties, Int64 PutFileOpt) at Microsoft.SharePoint.Deployment.FileSerializer.SetGhostedFile(Object fileOrListItem, SPLoggerObject loggerObject, SPWeb web, Guid existId, SPResourcePath fileUrl, SerializationInfoHelper infoHelper, SerializationInfoHelper infoHelperListitem, Boolean fileExistsInDb, Nullable`1 isLastVersion, StreamingContext context) clientRequestId: 1f3421bf-23fb-48aa-887a-e*** serviceRequestId: 77bf51a1-d04f-9****

Microsoft 365 and Office | SharePoint | For business | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

48 answers

Sort by: Oldest
  1. Anonymous
    2024-09-19T13:17:05+00:00

    Experiencing the same as Bart and Tadej and this flow and sharepoint file were created last week. Everything was working just fine but now getting the same error. Tried creating a new flow but no luck with that. Same error.

    Invalid number value.

    A number field contains invalid data. Please check the value and try again. CallStack -- at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)

    at Microsoft.SharePoint.Library.SPRequest.CreateOrUpdateFileAndItem(String bstrUrl, String bstrWebRelativeUrl, Guid& docId, Object punkDoc, Int32 docLength, Int32 exists, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Int32 iVersion, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String checkInComment, Int32 docLibRowID, String bstrListName, Int32 bNoExecute, SPFileSaveParams sfsp, Int32 bSkipModerateStatusCheck, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, Object& pvarMergedProperties)

    at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFileWithGuid(Stream spstm, SPLoggerObject loggerObject, SPWeb web, Guid fileId, SPResourcePath filePath, String fileValue, Int64 bytesInAzure, String quickXorHash, Int32 authorId, String authorLoginName, Int32& editorId, String editorLoginName, String checkinComment, DateTime& timeCreated, DateTime& timeLastModified, MetaInfoHandler metaInfo, Int64 length, Int32 iVersion, Boolean isFirstVersion, Nullable1 isLastVersion, SPImportSettings settings, Int32 listItemId, String listInternalName, Boolean hasNoExecuteFlag, ImportObjectManager objectManager, DecryptionInfo decryptionInfo, Nullable1 preserveExistingOnConflict, Nullable`1 createAntlerFile, Guid parentId, Object& propertyArray, Object& mergedMetaProperties, Boolean createStubFileOnly, Boolean forceNormalCobaltFile, IServiceQosInternalEvent blobCopyQosEvent, Boolean bypassQuotaCheck, Boolean performPostProcessing)

    clientRequestId: b7612a04-7e90-40a2-b647-6e2f225a82dc

    serviceRequestId: 01c951a1-5079-6000-6e8e-d403addc35ae

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-09-19T15:20:43+00:00

    The same error:

    "Valor de número no válido.\n\nUn campo de número contiene datos no válidos. Verifique el valor y vuelva a intentarlo. CallStack -- at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)\r\n at Microsoft.SharePoint.Library.SPRequest.CreateOrUpdateFileAndItem(String bstrUrl, String bstrWebRelativeUrl, Guid& docId, Object punkDoc, Int32 docLength, Int32 exists, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Int32 iVersion, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String checkInComment, Int32 docLibRowID, String bstrListName, Int32 bNoExecute, SPFileSaveParams sfsp, Int32 bSkipModerateStatusCheck, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, Object& pvarMergedProperties)\r\n at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFileWithGuid(Stream spstm, SPLoggerObject loggerObject, SPWeb web, Guid fileId, SPResourcePath filePath, String fileValue, Int64 bytesInAzure, String quickXorHash, Int32 authorId, String authorLoginName, Int32& editorId, String editorLoginName, String checkinComment, DateTime& timeCreated, DateTime& timeLastModified, MetaInfoHandler metaInfo, Int64 length, Int32 iVersion, Boolean isFirstVersion, Nullable1 isLastVersion, SPImportSettings settings, Int32 listItemId, String listInternalName, Boolean hasNoExecuteFlag, ImportObjectManager objectManager, DecryptionInfo decryptionInfo, Nullable1 preserveExistingOnConflict, Nullable`1 createAntlerFile, Guid parentId, Object& propertyArray, Object& mergedMetaProperties, Boolean createStubFileOnly, Boolean forceNormalCobaltFile, IServiceQosInternalEvent blobCopyQosEvent, Boolean bypassQuotaCheck, Boolean performPostProcessing)\r\nclientRequestId: fc3a7dfc-e896-40a4-88ed-fad4b83790fc\r\nservi

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2024-09-20T08:34:33+00:00

    Same here. Something seems to have changed after Sept 18 05:24PM - this was the last successful run of a flow which uses the Copy File action for a page. All runs in several flows which copy pages between sites have failed since then with the same error.

    I've done a lot SharePoint server-side development in the good old days and for me it seems that, there was a change in SharePoint (update of schema files or code) which causes the interal SSOM API call to fail when it "hits" the actual schema.

    The thing is: Opening a standard ticket for this as a customer is pure pain when explaining this to the 1st level support. Let's hope that the issue causes some important flows in large orgs to stop, so premium support gets fired up.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2024-09-20T09:27:29+00:00

    I'm also having this exact error. The automation was working perfectly fine yesterday and nothing had changed, but as of about 10 hours ago all of a sudden its broken and I'm getting the following:

    Invalid number value.

    A number field contains invalid data. Please check the value and try again. CallStack -- at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)

    at Microsoft.SharePoint.Library.SPRequest.CreateOrUpdateFileAndItem(String bstrUrl, String bstrWebRelativeUrl, Guid& docId, Object punkDoc, Int32 docLength, Int32 exists, String bstrCreatedBy, String bstrModifiedBy, Int32 iCreatedByID, Int32 iModifiedByID, Int32 iVersion, Object varTimeCreated, Object varTimeLastModified, Object varProperties, String checkInComment, Int32 docLibRowID, String bstrListName, Int32 bNoExecute, SPFileSaveParams sfsp, Int32 bSkipModerateStatusCheck, UInt32& pdwVirusCheckStatus, String& pVirusCheckMessage, Object& pvarMergedProperties)

    at Microsoft.SharePoint.Deployment.FileSerializer.CreateOrUpdateFileWithGuid(Stream spstm, SPLoggerObject loggerObject, SPWeb web, Guid fileId, SPResourcePath filePath, String fileValue, Int64 bytesInAzure, String quickXorHash, Int32 authorId, String authorLoginName, Int32& editorId, String editorLoginName, String checkinComment, DateTime& timeCreated, DateTime& timeLastModified, MetaInfoHandler metaInfo, Int64 length, Int32 iVersion, Boolean isFirstVersion, Nullable1 isLastVersion, SPImportSettings settings, Int32 listItemId, String listInternalName, Boolean hasNoExecuteFlag, ImportObjectManager objectManager, DecryptionInfo decryptionInfo, Nullable1 preserveExistingOnConflict, Nullable`1 createAntlerFile, Guid parentId, Object& propertyArray, Object& mergedMetaProperties, Boolean createStubFileOnly, Boolean forceNormalCobaltFile, IServiceQosInternalEvent blobCopyQosEvent, Boolean bypassQuotaCheck, Boolean performPostProcessing)

    clientRequestId: cc13b922-8a54-420a-b41e-5bd3a1e1c46b

    serviceRequestId: 6c0e52a1-b015-9000-f316-f644d1975893

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2024-09-20T14:17:00+00:00

    Same error with my flow that has been working fine for years before today.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments