I have a Windows Service application (developed in C++) running under Local System account. Operating system is Windows Server 2008 Standard - Service Pack 2 - 32-bit - 4Gb RAM.
Also running Office 2003 with Service Pack 3.
This service takes a RTF file and using DDE prints it with Microsoft Word. However Word fails to perform the print issuing an error (I can see the error if I enable interaction with desktop). The error is
"Run-time error '1001':
There is insufficient memory. Save the document now.
C:...\file.rtf"
A screenshot can be seen here: http://img804.imageshack.us/img804/9550/worderror.png
It used to work on Windows 2003.
Any idea? Suggestions? Could be permission related?
This is actually not supported by Microsoft: http://support.microsoft.com/kb/257757
Related
I experienced the following error after installing Information Server Console 8.1 on my windows xp sp2 workstation when I try to log on Information Server Console:
"Internal Error: - Failed to load the Java Virtual Machine. The most common cause of this error is a failure of Java virtual machine to allocate enough memory" Check the memory settings in ......\proxy xml.
I attached proxy.xml for your documentation. Besides my workstation has 4 Gb RAM and Sun Java Runtime Environment v 6.0_11.
"Other possible reasons for this failure are that one or more JARS are not present or some other configuration problem exists." Not very disclosing I suppose ...
I set the environment variables : XMOG_TRACE_LEVEL= Verbose and XMOG_TRACE_FILE=c:\xmogtrace.txt, tried to log on again, but no file or information is generated on c:\xmogtrace.txt and the error is the same.
Please see the following technote in ibm.com which discusses solution for this issue:
http://www-01.ibm.com/support/docview.wss?rs=14&uid=swg21370513
I wonder because running it on a client's minidump it reports a different Windows version than the client repeatedly told me she had, and the version I'm being reported happens to be exactly the same version I'm running WinDbg on.
So I wonder, can vertarget always be trusted (and clients not) or the information it relies on may be absent with some dump generation options and when it is it reports the version WinDbg is currently running on, or maybe just some default that happens to coincide with my OS version?
I'm using WinDbg 6.12.
In all my cases so far, vertarget has been correct and the customer/client made a mistake - and vertarget is one of the commands I use for every dump, exactly for the purpose of checking if the dump contains what I need.
But perhaps, things can potentially go wrong here as well, so let's evaluate some options:
vertarget also reports debug session time and system uptime. Do those also match your system? Reboot your system in order to get a low system uptime and check again. Is it still your PC's uptime?
vertarget also reports the number of CPUs. Does that number match your number?
Get a virtual machine which does not have your OS, e.g. one from Modern.IE (Microsoft). Copy WinDbg and the dump to the VM and check the output of vertarget again.
WinDbg 6.12 is a bit old. Do newer versions (6.2.9200 / 6.3.9600 or even 10.0) provide the same information or was there a bug fixed already?
And even check some other information:
Is it a dump of the correct application? Use | (pipe)
Is it a dump of the version you are expecting? Use lm vm <exename>
Does it have the flags which can be expected for the method used for taking the dump? Use .dumpdebug.
Other than that I observe (not representative) that many client OS version dumps (Windows 7, 8, 8.1) have all latest service packs installed, while administrators seem to follow the "never change a running system" approach for server OS (Windows Server 2012, R2). So it might just be a coincident.
We are migrating from Windows Server 2003 to Windows Server 2012. There are messages in private messagequeues on Windows Server 2003 that we need to move to Windows Server 2012. It's a one-time task.
The following 3 steps corrupted messagequeues on server 2012, and I had to uninstall and reinstall Message Queuing on Server 2012.
mqbkup -b c:\msmq_backup -y (on 2003)
Copy c:\msmq_backup from 2003 to 2012.
mqbkup -r c:\msmq_backup -y (on 2012)
http://technet.microsoft.com/en-us/library/cc773213%28v=ws.10%29.aspx
http://technet.microsoft.com/en-us/library/hh875586.aspx
I access these messagequeues and messages from .NET console and ASP.NET applications using System.Messaging Namespace.
http://msdn.microsoft.com/en-us/library/system.messaging%28v=vs.110%29.aspx
Any ideas would be appreciated. Thank you.
MQBKUP is not for moving to upgraded systems as it restores the old MSMQ configuration which, as you've found, won't necessarily be compatible.
If the computername is the same, you could try straight copying the LQS and Storage folders. On startup, MSMQ checks the address in the messages. If the address matches the local computername, the message will be loaded, otherwise discarded.
Of course, this assumes the MQ file format is the same in 2012 and, unfortunately, I haven't had a chance to look.
I am trying to install nservice bus on a fresh win server 2012 box and things are not working properly. Any help is appreciated..
I get setup failed prematurely and when I dumped into log file.. this is the error I get..
Calling custom action NServiceBus.Wix.CustomActions!NServiceBus.Wix.CustomActions.CustomActions.InstallMsmq
Installing/Starting MSMQ if necessary.
CustomAction InstallMsmqAction returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
Action ended 16:36:36: InstallFinalize. Return value 3.
Action 16:36:36: Rollback. Rolling back action:
Do I have to manually add MSMQ features.?
Yes you need to enable the MSMQ features first.
BTW, the MSI is really only to be installed on developers machines, to prepare a machine in production use the powershell cmdlets, see http://docs.particular.net/nservicebus/managing-nservicebus-using-powershell
Is your dev machine a WinServer 2012?
We have an application server with the following spec’s:
• Windows 2008 R2 operating system.
• All prerequisites are configures successfully and correctly: Windows roles, MSDTC and connection to SQL DB server.
• MS Reporting Services 2008 R2 are installed and configured successfully, and all reports are deployed and render with no problems.
The application server connects to SQL Server 2008 R2 DB on different server - there are no firewalls between the 2 servers , and using UDL file, the connection is always successful using windows authentication or SQL authentication on SQL Server.
When we install “K2 blackpearl 4.5 (4.10060.1.0) with Update KB001040”, the setup completes successfully but the following exception appears when we open work list, when K2 setup manager is opened for reconfiguration and when rendering any report on the report manager: “A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)” although all DB’s are created successfully during the installation for K2. Also all other features at K2 (any feature at Management Console) and Report Manager (deployment of reports, management of data sources, and folder/report settings) works perfectly.
When we remove K2 components from the server the reporting services works successfully again, without any reconfiguration.
We tried to move the server to new environment to check if there is a problem with the server itself, all installation and configuration are completed with no problems and the error message disappeared.
We did check all of below points:
• MSDTC configuration.
• All ports are open between the 2 servers.
• SQL connection is always successful between the 2 servers.
• We have a third server with MOSS 2007 installed and it works perfectly with problems in connection to DB.
• All users used for windows services and SQL windows connection are active and configured correctly.
o Have SQL login with dbcreator and SecurityAdmin roles.
o Are added as Administrators on Application server.
• We have tries Windows authentication and SQL authentication and they all gave the same problem.
• We have used a newer version of K2 installation files “K2 blackpearl 4.5 (4.10060.1.0) with KB001320” and it failed at the last steps of installation with the same problem.
Please help on this.
(full disclosure i work for K2) and looked through our system as well as the support forum and could not find a reference to this error. From the people i talked to it appears to be a general network issue, with quite a few possible causes, including something as simple as the network card. Although I am not 100% clear on a few points you made. When you said
"following exception appears when we open work list" Where are you opening the worklist from?
When you said
"When we remove K2 components from the server the reporting services works successfully again, without any reconfiguration."
Are you getting this error in SQL Reporting Services?
You can also post a question in http://k2underground.com someone else may have seen this.
Edit I asked around and there does not seem to be any good answers to this at the moment. Would you be willing to open a K2 support ticket and let us look at the K2 logs or see the config via livemeeting? Thanks!