Docusnap Support
Denisha Padley
Our competent and always helpful Docusnap support team can be reached via sup...@docusnap.com and via hotline +49 8033 6978-4545. Support requests are processed by our qualified support team as quickly as possible. You will receive the corresponding solution suggestions either by telephone or by email.
Do you have any questions about our licence models or prices? Our experienced and always friendly sales team will be happy to help you by email (in...@docusnap.com) or by telephone on +49 8033 6978-4500.
Unser kompetentes und stets hilfsbereites Docusnap Support-Team ist ber sup...@docusnap.com und via Hotline +49 8033 6978-4444 erreichbar. Supportanfragen werden von unserem qualifizierten Support-Team schnellstmglich bearbeitet. Sie erhalten die entsprechenden Lsungsvorschlge entweder telefonisch oder
per E-Mail.
Haben Sie Fragen zu unseren Lizenzmodellen oder Preisen? Dann hilft Ihnen unser erfahrenes und stets freundliches Vertriebs-Team per E-Mail (in...@docusnap.com) oder telefonisch +49 8033 6978-4000 gerne weiter.
If errors occur while using Docusnap, you can trace them. Check the Enable Debug Mode option in the Options dialog to log errors in the database. You have the option to either log all program events or exceptions only.
The Docusnap Server is required to schedule network scans, documentation creation processes, notifications, etc. to be performed automatically at a later time. To be able to analyze errors, the debug mode for the Docusnap Server component must be enabled.
You can do so in the Configuration wizard for the Docusnap Server. To set the desired level of debugging, you can select either Log everything or Exceptions only from the Debug Level dropdown list. The storage location is set to Database. Clicking the Reset Log button will delete all existing error information from the database.
Send with Outlook: Opens the standard e-mail client and creates a new e-mail. MAPI support is required. The recipient defaults to the Docusnap Support Team and the log file is attached automatically. Alternatively you can also save the log file first, manually create an e-mail addressed to the Docusnap Support team and attach the log file.
The 4me Docusnap Connector makes it possible for organizations to connect and manage items of specific service management interest. It is fully configurable, allowing organizations to specify Docusnap data that they want to see in the CI records of their 4me account.
Techwork can provide the 4me Docusnap Connector as a service, without the need for customer infrastructure components, or as an on-premise installation, for customers that run Docusnap within their own organizational network.
Download the 4me Docusnap Connector datasheet for more information about this integration.
Before joining 4me as Service Management Architect, Fred was CTO at Fruition Partners Northern & Central Europe (part of DXC Technology Company) where his primary focus was helping CIOs of large European enterprises get a solid grip on their service provision and enabling them to support the digital enterprise.
4me combines ITSM with ESM and SIAM capabilities, enabling all internal departments, such as IT, HR, and Facilities, as well as external managed service providers, to work seamlessly with each other. At the same time, 4me provides complete visibility and control of service cost and quality.
Callie, I have downloaded the program and I am going to attempt to start testing it out today. I have so many tasks going on that time is not on my side but I need something to work really bad right now. I will let you know.
Callie, I am looking for help on creating contract in this software and I have an appointment for a webinar on Wednesday, but I want to do some testing before then. The US number for support only rings and I am trying to reach someone to ask a couple of questions too? Do you know how to reach someone? I think my phone system blocks outgoing to (49) phone codes.
So far it looks like this software has the features I need to manage the licensing and contracts. Seems the cost could go either way based on the amount of devices you have. in my case I saw the $800 for premium (which is what I need) but when you look closer that is up to 50 AD objects for Windows/Mac/Linux. I have around 450 objects and it will cost around $7000 plus maintenance. This is not bad considering what it can do, but I have just invested quite a bit in Express Metrix but unfortunately it is not helping me right now. I will run the trial version and see if everything I need is there, just not sure about the cost.
I have been in contact with support. Still working on making sure I can get the contracts created I need with reports for what I want to see. Pricing, I will contact someone once I know I can get the data out that I need. If I have to struggle to get the data out in a usable format, then I am back to where I started and it will look like Excel will be my best option.
The biggest challenge in discovery is the classification and typing of SNMP-enabled network devices, as the SNMP protocol does not provide information about the device class and type. Through years of experience and support of Docusnap users, we are able to identify and record a variety of device types according to the purpose of use.
Currently, there are three basic SNMP versions. SNMPv1, SNMPv2 and SNMPv3: SNMPv1 and SNMPv2 do not use encryption algorithms to transmit data. SNMPv3, on the other hand, supports security solutions such as user accounts, authentication, or encryption. Because of these differences, Docusnap365 has SNMPv1/-v2 and SNMPv3 wizards for discovery.
SNMPv3 expects logon information to be transmitted in encrypted form when logging on. In the SNMPv3 wizard the properties User, Auth. Algorithm, Auth. Password, Private Algorithm, Private Password and Context Name are available.
Digitalization affects asset management just as much as any other area. This calls for suitable solutions and wide-ranging expertise to efficiently manage business assets. With this in mind, SVA has built up its own team of experts that can take a broad view of two core issues.
SVA has many years of experience and outstanding expertise in hardware and software, as well as their implementation. Together with our technical experts and experienced business process consultants, the asset management competence center provides customers with all-round support all the way to operational launch.
This is one of two errors we are seeing after migrating our REST api workloads to onestream's Azure environment. It happens fairly frequently, albeit in an unpredictable way. I haven't found a pattern yet. It doesn't happen on-premise.
If anyone has experience deploying a REST api solution to Azure, please let me know if this is an error message you encounter frequently. It may not even be a problem with onestream's software; perhaps the root cause is with the Azure load-balancer. I am also looking into other possible explanations, like SSL inspection. Any tips would be greatly appreciated!
The error indicates a parsing problem at a certain character position within the results. Basically what we are seeing is that the json payload that is being delivered via the REST api is unexpectedly truncated. As a result, we lose some portion of the data, and the JSON reader is unable to interpret the entire document.
Please let me know if anyone has encountered this type of a REST api issue after migrating to Azure.
System.Exception: 'Invalid response from query in SendHttpRequest. Status code is Unauthorized. Content is "Error processing External Provider Sign In information. The remote name could not be resolved: 'login.microsoftonline.com'". '
This occurs AFTER we have used the AAD to authenticate and calculate an oauth bearer token. It happens within the subsequent request to the REST api. What this is essentially saying is that the onestream application server in Azure is not able to contact "login.microsoftonline.com". Or rather, it can't even resolve the I.P. address for login.microsoft.com.
Obviously it is a problem if/when any application that is hosted in Azure is unable to contact an identity server that is also hosted in Azure. I'm assuming the purpose of contacting that identity server is to validate the oauth bearer token in the request header.
If anyone is familiar with this error, or with the resolution, please let me know. Migrating our onestream platform to Azure has been an interesting experience, with quite a few challenges. We are opening support tickets as well, but new problems seem to be coming up faster than we can fix them. If onestream support is able to find fixes to these, I will remember to circle back with a reply for the forum.
They are all precise infrastructure issues that are better discussed with our Support guys; so to start with, reading you've already opened tickets, I was tempted to just archive them. However, from the perspective of forum readers, who are mostly application administrators and application developers, they all originate from using the REST api in Azure and the reliability challenges that arise from that scenario - I think you understand that, considering you've effectively linked them together with that "part 1/2/3" in the title. So I thought there was the chance of a useful strategic discussion if we framed it like that. I'm really sorry if it looks harsh; I'm just trying to keep this space look more like a discussion area than a support-ticket queue.
c80f0f1006