We are facing a problem with Word Automation Services in Sharepoint 2010. We have a workflow, which queues a conversion job (docx to pdf). In our dev environment, everything works well, but in production, a strange error occurs. No error shown anywhere, but file is simply not created. The only diagnostics is, that it puts error number 131172 to Items table in Word Automation Services database.
Nothing goes to SP log (log level set to information) and nothing to event log. Our error number is not listed in documentation. Timer is up and running..
Piece of code which queues job (nothing very special):
ConversionJobSettings jobSettings;
ConversionJob pdfConversion;
string wordFile;
string pdfFile;
jobSettings = new ConversionJobSettings();
jobSettings.OutputFormat = SaveFormat.PDF;
jobSettings.MarkupView = MarkupTypes.Text;
pdfConversion = new ConversionJob("Word Automation Services", jobSettings);
pdfConversion.UserToken = web.CurrentUser.UserToken;
pdfConversion.AddFile(wordFile, pdfFile);
pdfConversion.Start();
Have anyone seen this kind of error?
We had the same problem on Czech version of SharePoint 2019, which was resolved by installing English language pack.
Related
I have a problem with my Outlook addin.
First of all, a very very simple overview of the workflow:
The addin is supposed to get a folder list from the exchange server (public folders).
The user can select one of this folders.
The folderid of the selected public folder will be converted from the IdFormat EwsId to HexEntryId to get the mapifolder afterwards.
Then the user can open the folder in Outlook. This is done by setting the this.Application.ActiveExplorer().CurrentFolder.
The complete code:
// _service is an instance of ExchangeService (Microsoft.Exchange.WebServices.Data)
// The publicFolder is the selected public folder (type of Microsoft.Exchange.WebServices.Data.Folder)
var objAltPublicFoldId = new AlternatePublicFolderId(IdFormat.EwsId, publicFolder.Id.UniqueId);
var objId = (AlternatePublicFolderId)_service.ConvertId(objAltPublicFoldId, IdFormat.HexEntryId);
var outlookFolder = Application.Session.GetFolderFromID(objId.FolderId);
this.Application.ActiveExplorer().CurrentFolder = outlookFolder;
Most of the time this works good. But some users are getting an error while trying to open the folder.
The exception is always thrown by the method to get the mapifolder object ( Application.Session.GetFolderFromID(objId.FolderId);).
The error message is:
the message interface returned an unknown error if the problem persists restart outlook
But again, this only happens for a few users, but once a user goets this error there is a great chance that this problem will persist until the complete Office installation has been reinstalled. I haven't found any other way to fix this issue so far and the problem seems to come out of nowhere.
All I've found out so far is that the objId.FolderId always contains the correct value, and that this affects all folders, not only a specific one. But the user can manually open the folder in Outlook.
The Outlook versions of the affected people are 2016 and 365.
The affected assembly is the Microsoft.Office.Interop.Outlook.
The reference to this assembly has following properties:
Description: Microsoft Outlook 16.0 Object Library
Filetype: ActiveX
Identity: {00062FFF-0000-0000-C000-000000000046}\9.6\0\primary
Path: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.Office.Interop.Outlook\15.0.0.0__71e9bce111e9429c\Microsoft.Office.Interop.Outlook.dll
Version: 9.6.0.0
I really hope that there is someone who's had the same issue and found a solution for that.
Right now, anything could be the source of the error. The Exchange Server, the network, outlook, the Microsoft.Office.Interop.Outlook assembly, the enabled cached mode.
In my ASP .Net application, I am using 'PDFTron 6.6.0.38591'.
We are using following code to convert Office documents to XOD:
string fileName = Path.GetFileName(pdfTronServiceRequest.FilePath);
fileName = ConstructConvertionFileName(fileName);
outFileName = Path.Combine(outputPath, fileName);
pdftron.PDF.Convert.ToXod(pdfTronServiceRequest.FilePath, outFileName);
response.Result = outFileName;
This code works well for filetypes like docx, xlsx, however for Powerpoint files, no response is returned(request timed out).
On checking the Task Manager window, we can see that a process for 'POWERPNT.exe' is started. However, this process never ends up itself(unlike that in case of word, excel upload).
Also, if I manually ends up this process, the conversion to XOD is successful and response is coming out correctly.
Also, please note that we are facing this issue only when we deploy the code on our test environments. Locally, PPT upload is working fine.
Let me know if you need any other information.
First, you should be running a licensed version of PowerPoint, not a trial/eval one. In particular, the account (including a Service/App Pool account) needs to have accepted the MS office licensing to make sure Office is a fully licensed product.
Also, is this happening with any ppt file or only certain ones? If certain ones, then try using one of the following two flags.
pdftron.PDF.Convert.Printer.SetMode(mode)
e_printer_only
e_interop_only
Finally, switch to the latest version. Which at the very least should provide a lot more debugging info in the exception message.
I am having an issue with opening a document using Microsoft Word from ASP.NET MVC.
This works perfectly on my developer machine, but not when deployed to IIS.
Dim word = New Microsoft.Office.Interop.Word.Application
'This line is failing to return a document object
Dim letter = word.Documents.Add(letter_doc_path)
'This line then fails due to [letter] being null
letter.MailMerge.OpenDataSource(csvPath)
I have added permissions in "Component Services" (dcomcnfg) to the NETWORK SERVICE user which allows the creation of the Word object in the first place, but I am completely stuck as what to do with this one.
I have also tried suppressing Word dialogs with the following line just in case
word.DisplayAlerts = Microsoft.Office.Interop.Word.WdAlertLevel.wdAlertsNone
The issue isn't helped by not having an error (apart from the null object reference obviously) - maybe there's a way to query Word for a specific error message?
Word requires the normal.dot template file when opening any document, the problem was occurring because the IIS user didn't have anywhere to create the normal.dot so it was failing in the background.
This was fixed by setting the UserTemplate path for the newly created word instance (immediately after creating it).
The path must be writeable by the IIS user (NETWORK SERVICE in my case).
word.Options.DefaultFilePath(Microsoft.Office.Interop.Word.WdDefaultFilePath.wdUserTemplatesPath) = working_folder
So just for completeness, here's the original example with the winning line included:
Dim word = New Microsoft.Office.Interop.Word.Application
'this line fixed it
word.Options.DefaultFilePath(Microsoft.Office.Interop.Word.WdDefaultFilePath.wdUserTemplatesPath) = working_folder
Dim letter = word.Documents.Add(letter_doc_path)
I was having the same problem, and the settings that wheelibin suggested weren't enough to create documents using the NETWORK SERVICE account.
What I ended up doing is:
Create a user account for this
process to run under.
Login as the user and run Word (this
does various setup tasks in Word so
the application doesn't try putting
up modal dialogs when running as a
service).
Create a new application pool and set
the pool to run as the user account.
If you're using Windows
Authentication, and your server is
Windows 2003 (or 2000, presumably),
then this issue applies, and you
need to either change the SPN of the
server, which will break Windows
Authentication for any application
running under a different user
account, or you have to switch the
authentication provider over to NTLM
instead of Kerberos.
IIS 7 can use Kernel Mode Authentication to avoid the issue.
I am not sure how are you catching the errors.
Please take a look at the following pages if you find some clue from that.
Error while using Microsoft Office 2003 in web application
Error while calling MS-Word from ASP.NET
"There is insufficient memory or disk space. Save the document now" - Opening MS Word from ASP.NET
I am using Document imaging library for parsing text from image. My code is working fine on local but facing problem while deploying in windows server 2003.
Can anyone help me on this?
Make sure MODI is installed(it will be there in MS Office Tools if installed).If not go through the link and install(http://www.mydigitallife.info/how-to-open-mdi-microsoft-document-imaging-format-with-office-2007/).if Still you r getting same error then try this
1)Go to IIS->ApplicatioPools->Default Applicationpool->Identity->custom account->Give the user name and password.
I am working on integrating my company's product with Jira so users can log bug reports directly from the application. Everything was wqorking smoothly so i decided to import the data from our live Jira system into my development system so that i had some real world data to play with. Since then when i try to get an authtication token it throws the following exception "com.atlassian.crowd.exception.PasswordEncoderNotFoundException: The PasswordEncoder 'atlassian-security' was not found in the Internal Encoders list by the PasswordEncoderFactory". I have checked and the Atlassian Security Password Encoder is enabled in the Crown Password Encoders plugin.
My code is super simple just an ASP.net based text based issues search with the results wired to a grid view code as below:
JiraSoapServiceService service = new JiraSoapServiceService();
string token = service.login("integration", "test");
if (!string.IsNullOrEmpty(txtSearch.Text))
{
RemoteIssue[] issues = service.getIssuesFromTextSearchWithLimit(token, txtSearch.Text, 0, 100);
gvwIssues.DataSource = issues;
gvwIssues.DataBind();
}
I get the error on the call to service.login, it worked fine before I imported the live data. And yes i did add the integration user again after i had imported the data.
Anyone any ideas on this.
No idea what was causing this but rebooting the PC that the dev Jira was installed on fixed it.
EDIT
I have had this a few times now. It tends to happen when you do something like restart the SQL server, restore the jira database via SQL server, restore jira via the inbuilt XML file import method or similar. You don't have to restart the machine just the jira windows service. No idea if this is a problem with other DBs or server types.