I am using Redemption 5.0.2 and I get this error when I attempt to read the RDOMail CreationTime and ReceiveTime in Quick view:
{"Exception has been thrown by the target of an invocation."}
and this error when the code executes the line:
System.Runtime.InteropServices.COMException: 'System Error. Code: 18.
There are no more files'
We are attempting to migrate to Windows 10 and Office 365 any help would be appreciated.
This is a problem with the older versions of Redemption and a Windows update missing some timezone resource files. You need to use the latest version of Redemption.
Related
We use a product from Epicor, I believe developed by mProof, called Clientele ITSM. The version we are using is 2016.2. We moved to Office 365 and since then are experiencing the error that started with Windows 10 (1809). The error message we receive from the application is:
System.Runtime.InteropServices.COMException (0x8000FFFF): System Error. Code: 18.
There are no more files
at Redemption.ISafeMailItem.SaveAs(String Path, Object Type)
at Clientele.Modules.Attachment.Client.Forms.AttachmentStatusBarPanel.AddEmailAsAttachment(MailItem mitem, Int32 numberOfEmailsSelected)
at Clientele.Modules.Attachment.Client.Forms.AttachmentStatusBarPanel.HandleDragDropEmail()
at Clientele.Modules.Attachment.Client.Forms.AttachmentStatusBarPanel.AttachmentStatusBarPanel_DragDrop(Object sender, DragEventArgs e)
I'm looking to see if there is a way to update the version of Redemption without upgrading the Clientele ITSM application? The DLL appears to be Interop.Redemption.DLL, and the version is 5.15.0.0.
I realize this is a long shot, and the likely correct answer is to upgrade the version of Clientele ITSM, but that is unfortunately not an option at this time.
Thanks for any help or advice.
Interop.Redemption.DLL is just a binary header file used by .Net. The files you need to replace are redemption.dll and/or redemption64.dll. They can be swapped without updating the application that uses it - all versions of Redemption are backward compatible.
Recently I have installed Xtext and tried to run the default Hello world! code using the tutorials available on youtube. However, when I try to run the code I am getting 44 errors.
I am new to using Xtext as well as eclipse. I have tried to reinstall eclipse a lot of times. I have tried with normal version, enterprise version and DSL tools version. But every time I am getting the same errors. Please help me resolve this issue. I tried to find out what these errors meant and how to resolve them over the eclipse community forums but did not find any solution.
All the errors are repetitions of the following two errors.
Description Resource Path Location Type
Duplicate field InternalMyDslParser.FOLLOW_ InternalMyDslParser.java /org.xtext.example.mydsl.ide/src-gen/org/xtext/example/mydsl/ide/contentassist/antlr/internal line Java Problem
and
Description Resource Path Location Type
Syntax error on token "?", delete this token InternalMyDslParser.java /org.xtext.example.mydsl.ide/src-gen/org/xtext/example/mydsl/ide/contentassist/antlr/internal line Java Problem
Please Help me resolve this issue.
Let me give you some background what I'm trying to achieve before I call out the problem.
Use TFS API to Get Services Work Item.
Get all the Open Bugs.
Write in excel all the Open Bugs (from step2).
Send step3 Excel as Attachment through SMTP.
Schedule a Windows Task on Windows Server 2012 and X64 to perform above steps on daily basis.
Problem:
While running step5 I'm not able to write into Excel using OLEDB because of exception"The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine". To resolve this issue, I have build my project Platform Target=X64.
The excel issue is resolved but I'm not able to access TFS API because it is not able to load DLL Microsoft.TeamFoundation.WorkItemTracking.Client.DataStoreLoader.
Kaleem.
If you get the following error message: "Could not load file or assembly ‘Microsoft.TeamFoundation.WorkItemTracking.Client.DataStoreLoader’ or one of its dependencies. An attempt was made to load a program with an incorrect format". Please take the solution described in this blog: http://www.tonicodes.net/blog/installing-and-configuring-odata-service-for-tfs-11/
I have a Windows service that is package into an MSI via Visual Studio 2010 Setup Project. This has worked well for years, and we typically installed this service on a Windows Server 2003 machine. Now we're upgrading to a Windows Server 2012 machine and getting an error message when installing this program:
'QuickReportsEmailerService' is not a valid short file name.
This prevents the program from being installed. I tried changing the ProductName in my setup project to QREmailerService but then the error message just changes to:
'QREmailerService' is not a valid short file name.
I executed my installer with the /lv options and I get this output:
The installer has encountered an unexpected error installing this
package. This may indicate a problem with this package. The error code
is 2835. The arguments are: ErrorIcon, ErrorDialog, MSI (c) (68:F0)
[14:34:41:379]: Product: QREmailerService -- Error 1325.
'QREmailerService' is not a valid short file name.
Action ended 14:34:41: CostFinalize. Return value 3. MSI (c) (68:F0)
[14:34:41:379]: Doing action: FatalErrorForm Action start 14:34:41:
FatalErrorForm. MSI (c) (68:F0) [14:34:41:379]: Note: 1: 2235 2: 3:
ExtendedType 4: SELECT Action,Type,Source,Target, NULL,
ExtendedType FROM CustomAction WHERE Action = 'FatalErrorForm'
What do I need to change in order to get this installed?
Some more info:
I'm an administrator on the server
I saw some similar errors when I Googled this, but they all suggested I modify this registry key. But I checked what they were changing it to, my registry key was already in that format.
Edit-
I fixed the problem by changing the ProductName to "QR". But that's hardly acceptable, now it's not descriptive enough. Why is it getting mad? Is there some maximum length of a ProductName I should know about?
Figured it out.
So my setup project had the application folder default to: D:[ProductName]
But our new 2012 server doesn't have a D drive, I want to install on E drive. So I changed that in the setup project to be C:[ProductName]. C drive exists, so now in the installer UI I just have to manually change to E drive.
Not sure why it worked with D:[ProductName] when the ProductName was just "QR" but oh well.
We are trying to move an old client application from one PC to a new windows 7 64 bit PC. At the time the software was developed we used QBFC version 5 to interact with quickbooks, however it appears now that we can no longer do so. I attempted to register the interop.qbfc5lib.dll after installing the QBFC5 installation package and we still receive an error message. I've also attempted installing the most recent version of the SDK to the system and upgraded the QBRPXML2 to the most recent version. The client is now running QB2013 on the server and has updated his data to this version.
The error we are receiving is: "Retrieving the COM class factory for component with cLSID {4877276c-486d-b201-f096035ca4df} failed due to the following error: 80040154.
Suggestions other than recompile the code?
I had this problem with a client who I had used QBFC 8 and he had switched to a new computer. I didn't do a lot of research, but it appears that the installers that Intuit has on their websites use different CLSID than I originally had built against. I just downloaded and installed QBFC 5, which I didn't have anything installed for, and it shows the following CLSID in the registry (I'm on Windows 7 64-bit):
QbFC5.QBOESessionManager {86AC2FAD-C987-4757-B591-02F9867A8BE5}
QbFC5.QBSessionManager {4877276C-A727-486D-B201-F096035CA4DF}
The only thing I can think of is that the COM files that were originally installed on your development machine have been changed in a later installation. For my client on QBFC8, I simply switched to using QBFC12 and recompiled the code.