Goline Logo



  • Route RPKI validation April 1st, 2022
    RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...
  • RIPE – Atlas Anchor February 17th, 2022
    We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems.https://atlas.ripe.net/probes/7073/RIPE Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
  • MANRS June 20th, 2020
    GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

SharePoint2016: problema: File bloccato da un altro utente

La situazione non è ancora chiara e visto che il problema si è presentato una sola volta e non è stato possibile riprodurlo.
È stata eseguita la seguente operazione:
La procedura é sperimentale e deve ancora essere testata ulteriormente su casi reali.
Se non è urgente attendere da 10 min a qualche ora prima e provare a riaccedere
Per individuare il file bloccato:
collegarsi a SQL di SPP2016 
Verificare che il file sia bloccato. Cercare lo stato del campo CheckoutUserID
SELECT  CheckoutUserID FROM [Nome del database].[dbo].[AllDocs] where LeafName like '%NomeDelFIle%'
Se il campo non é NULL vuol dire che é bloccato
IMPORTANTE: controllare che il files sia solo uno. Se vengono individuati più record nella stessa cartella vuol dire che il vile è stato Estratto prima di essere usato. Quindi prima di tutto eseguire la procedura di “Annulla estrazione”
Fare una copia del file in locale, almeno per avere una versione, anche se non è la più recente.
Impostare il campo CheckoutUserID , CheckoutDate , CheckoutExpires a NULL
Update [Intranet.goline.ch].[dbo].[AllDocs] set CheckoutUserID = null where LeafName = 'NomeDelFIle'
Update [Intranet.goline.ch].[dbo].[AllDocs] set CheckoutDate = null where LeafName = 'NomeDelFile'
Update [Intranet.goline.ch].[dbo].[AllDocs] set CheckoutExpires = null where LeafName = 'NomeDelFile'
La procedura é sperimentale e deve ancora essere testata ulteriormente su casi reali.
Se non è urgente attendere da 10 min a qualche ora prima e provare a riaccedere

0 0 votes
Article Rating
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x