Sharepoint log files growing huge

Once again a SharePoint question :)
I ran the following script against our SharePoint 2013 farm:
#Specify the location of the CSV file here.
$r = Import-Csv C:\folder\users.csv
foreach($i in $r){
#The following line displays the current user.
Write-Host "The URL is:"$i.Url
#Disables the "Minimal Download Strategy" feature under "Site Features".
#Disable-SPFeature -Identity "MDSFeature" -Url $i.Url -force -confirm:$false
#Enables the "SharePoint Server Publishing" feature under "Site Features".
Enable-SPFeature -Identity "PublishingSite" -Url $i.Url -force -confirm:$false
#Enables the "SharePoint Server Publishing Infrastructure" feature under "Site Collection Features".
Enable-SPFeature -Identity "PublishingWeb" -Url $i.Url -force -confirm:$false
The csv file that is being imported contains about 2000+ rows with users' MySite links where we want to en-/disable several features.
The script does what it is supposed to do, but while running the script and reaching user No. ~15 the log files under "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\LOGS" starts to grow huuuuuuge (~5GB).
They are mostly filled with this:
09/17/2014 11:04:27.72 PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable Potentially excessive number of SPRequest objects (18) currently unreleased on thread 6. Ensure that this object or its parent (such as an SPWeb or SPSite) is being properly disposed. This object is holding on to a separate native heap.This object will not be automatically disposed. Allocation Id for this object: {D5F7BC80-8C88-4E17-9985-782F9724F2B9} Stack trace of current allocation: at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout, Boolean bAsAnonymous) at Microsoft.SharePoint.SPWeb.InitializeSPRequest() at Microsoft.SharePoint.SPWeb.EnsureSPRequest() at Microsof... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...t.SharePoint.SPWeb.SetAllowUnsafeUpdates(Boolean allowUnsafeUpdates) at Microsoft.SharePoint.SPPageParserNativeProvider.<>c__DisplayClass1.<UpdateBinaryPropertiesForWebParts>b__0() at Microsoft.SharePoint.SPSecurity.RunAsUser(SPUserToken userToken, Boolean bResetContext, WaitCallback code, Object param) at Microsoft.SharePoint.SPPageParserNativeProvider.UpdateBinaryPropertiesForWebParts(Byte[]& userToken, Guid& tranLockerId, Guid siteId, Int32 zone, String webUrl, String documentUrl, Object& registerDirectivesData, Object& connectionInformation, Object& webPartInformation, IntPtr pWebPartUpdater) at Microsoft.SharePoint.Library.SPRequestInternalClass.EnableModuleFromXml(String bstrSetupDirectory, String bstrFeatureDirectory, String bstrUrl, String bstrXML, Boolean fForceUng... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...host, ISPEnableModuleCallback pModuleContext) at Microsoft.SharePoint.Library.SPRequestInternalClass.EnableModuleFromXml(String bstrSetupDirectory, String bstrFeatureDirectory, String bstrUrl, String bstrXML, Boolean fForceUnghost, ISPEnableModuleCallback pModuleContext) at Microsoft.SharePoint.Library.SPRequest.EnableModuleFromXml(String bstrSetupDirectory, String bstrFeatureDirectory, String bstrUrl, String bstrXML, Boolean fForceUnghost, ISPEnableModuleCallback pModuleContext) at Microsoft.SharePoint.SPModule.ActivateFromFeature(SPFeatureDefinition featdef, XmlNode xnModule, SPWeb web) at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionModules(SPFeaturePropertyCollection props, SPSite site, SPWeb web, SPFeatureActivateFlags activateFlags, Boole... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...an fForce) at Microsoft.SharePoint.Administration.SPElementDefinitionCollection.ProvisionElements(SPFeaturePropertyCollection props, SPWebApplication webapp, SPSite site, SPWeb web, SPFeatureActivateFlags activateFlags, Boolean fForce) at Microsoft.SharePoint.SPFeature.Activate(SPSite siteParent, SPWeb webParent, SPFeaturePropertyCollection props, SPFeatureActivateFlags activateFlags, Boolean fForce) at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureCollection.CheckSameScopeDependency(SPFeatureDefinition featdefDependant, SPFeatureDependency featdep, SPFeatureDefinition featdefDep... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...endency, Boolean fActivateHidden, Boolean fUpgrade, Boolean fForce, Boolean fMarkOnly) at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependency(SPFeatureDefinition featdefDependant, SPFeatureDependency featdep, Boolean fActivateHidden, Boolean fUpgrade, Boolean fForce, Boolean fMarkOnly, FailureReason& errType) at Microsoft.SharePoint.SPFeatureCollection.CheckFeatureDependencies(SPFeatureDefinition featdef, Boolean fActivateHidden, Boolean fUpgrade, Boolean fForce, Boolean fThrowError, Boolean fMarkOnly, List`1& missingFeatures) at Microsoft.SharePoint.SPFeatureCollection.AddInternal(SPFeatureDefinition featdef, Version version, SPFeaturePropertyCollection properties, SPFeatureActivateFlags activateFlags, Boolean force, Boolean fMarkOnly) at Microsoft.SharePoint.S... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...PFeature.ActivateDeactivateFeatureAtSite(Boolean fActivate, Boolean fEnsure, Guid featid, SPFeatureDefinition featdef, String urlScope, String sProperties, Boolean fForce) at Microsoft.SharePoint.SPFeature.ActivateDeactivateFeatureAtScope(Boolean fActivate, Guid featid, SPFeatureDefinition featdef, String urlScope, Boolean fForce) at Microsoft.SharePoint.PowerShell.SPCmdletEnableFeature.UpdateDataObject() at Microsoft.SharePoint.PowerShell.SPCmdlet.ProcessRecord() at System.Management.Automation.CommandProcessor.ProcessRecord() at System.Management.Automation.CommandProcessorBase.DoExecute() at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automati... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...on.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) at lambda_method(Closure , Object[] , StrongBox`1[] , InterpretedFrame ) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0) at System.... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...Management.Automation.DlrScriptCommandProcessor.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess) at System.Management.Automation.CommandProcessorBase.DoComplete() at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(CommandProcessorBase commandRequestingUpstreamCommandsToStop) at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext) at System.Management.Automation.Interpreter.ActionCallInstruction`6.R... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...un(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.Interpreter.Run(InterpretedFrame frame) at System.Management.Automation.Interpreter.LightLambda.RunVoid1[T0](T0 arg0) at System.Management.Automation.DlrScriptCommandProcessor.RunClause(Action`1 clause, Object dollarUnderbar, Object inputToProcess) at System.Management.Automation.CommandProcessorBase.DoComplete() at System.Management.Automation.Internal.PipelineProcessor.DoCompleteCore(CommandProcessorBase commandRequestingUpstreamCommandsToStop) at System.Management.Automation.Intern... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...al.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate) at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper() at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc() at System.Management.Automation.Runspaces.PipelineThread.WorkerProc() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart... 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
09/17/2014 11:04:27.72* PowerShell.exe (0x235C) 0x2B44 SharePoint Foundation Performance naqx Monitorable ...() 5b7cf973-1e3f-4985-bdf8-598eecf86ab6
I tried finding something on the internet on this but either my Google Mojo is gone or there is no one else posting about this.
Since we do not want to change the logging behavior of SharePoint (unless it is really necessary), I'd like to know if there is something wrong with my code? Is there some parameter I can use to suspend logging for this script? There must be something I'm
doing horribly wrong :(
Thanks in advance!
(If anything I posted is unclear please let me know since English isn't my first language)
EDIT: There is nothing productive happening on that farm. There is a web application for the MySites and one for a publishing portal (without any significant content).

It's because MS did a poor job on the SharePoint object model. You shouldn't need to call a 'dispose' method on any object in .Net, the garbage collector should automatically identify a no-longer required object and remove it. Unfortunately, and there might
be a reason for it, that isn't true for SPWeb or SPSite objects.
Evidently the Enable-SPFeature comandlet contains a SPSite or SPWeb object and fails to dispose of it.
You could try using Start-SPAssignment: http://technet.microsoft.com/en-us/library/ff607664%28v=office.15%29.aspx which some have found to be useful to deal with this. Another option would be to create a process that generates a new thread for each row in
the csv which will result in the objects being destroyed as that process ends.

Similar Messages

  • 903/Enterprise; log files grow boundlessly and weekly bounces are needed

    This feed back is the result of an eval of 903 IAS
    enterprise on Solaris, 2 box cluster.
    This feed back is FYI.
    After installing IAS Enterprise 903 many times, testing
    stop/start/reboot use cases I noticed that many internal
    log files grow boundlessly.
    I've seen the notes on turning down log levels. This
    is still far from adequate. Log files in a 24x365
    architecture must be managable and have finite maximum disk
    space consumption sizes setable.
    Framework error events also need to be hooked into an Enterprise
    error and alert protocol. SNMP is not my favorite, but it's
    a start. JMX is my favorite. Also check out the free
    Big Brother monitor; www.bb4.com and it's wire protocol.
    Thanks and best of luck,
    Curt

    Just curious whether other folks have any opinions on
    OEM's suitability for a high rel. environment?
    On log file management?
    curt

  • Transactional log file grow

    hello,
     how we will solve the problem in this scenario,
    1) I configured mirroring 
    2)my mirror database is full & not available to take any more transactions from principle
    3) so, that transaction log is growing up in principle.

    Have you ever done a trx log backup on the principle?
    No, I have not done trx log backup on the principle.
    ok I will take log backup
    then  I can see that mirroring is paused or suspended ,I can resume mirroring .
    what would happen if there is no space in mirror database? 
    whether I need to reconfigure my mirroring by dropping mirror database or else can I add any disk space to mirror database? 

  • Fatal NI connect error 12203 resulting huge increase in sqlnet.log file

    Hi,
    I am getting the following error message in SQLNET.LOG file on the client machine. This is my upload program which takes few hours to complete and during the program run, the size of SQLNET.LOG file keeps on increasing and goes to 100's of MB and it contains only this error repeatedly.
    But my program gets connected to Database and does the upload. But the size of SQLNET.LOG file grows like anything. Pls let me know what's going wrong.
    ERROR in SQLNET.LOG File -
    Fatal NI connect error 12203, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle80)(ARGV0=oracle80ORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=C:\ORAWIN95\BIN\IFRUN60.EXE)(HOST=IT_DBA)(USER=IT))))
    VERSION INFORMATION:
         TNS for 32-bit Windows: Version 8.0.5.0.0 - Production
         Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.0.4.0.0 - Production
         Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 8.0.5.0.0 - Production
    Time: 06-MAR-03 12:37:08
    Tracing not turned on.
    Tns error struct:
    nr err code: 12203
    TNS-12203: TNS:unable to connect to destination
    ns main err code: 12560
    TNS-12560: TNS:protocol adapter error
    ns secondary err code: 0
    nt main err code: 102
    TNS-00102: Keyword-Value binding operation error
    nt secondary err code: 0
    nt OS err code: 0
    Regards,
    Mitesh V.

    Hi,
    Actually I thought this error is appearing in only one of the machines, but when I am figuring out, I found the same error in almost all the client machines.
    Though the programs are running fine getting the database connectivity, I am not able to find why it is giving error showing connection through BEQ protocol.
    Pls someone tell me why this is happening and how I will find out which protocol it is using.
    Regards,
    Mitesh Vijayvargiy

  • Log File dev_server0 excessively growing over time

    Hello everybody,
    I was facing an interesting crash of the XI system recently. The hard disk of the server went full and nothing worked anymore. After some investigation I found out that the file dev_server0 was growing excessively up to several GB of size.
    After stopping the engine, deleting the file and starting again, everything worked fine but the file continues to grow again.
    Can anybody tell me, what could be wrong with this file? Is there some kind of logging I accidentally enabled that fills up this file - or does this look like a defect rather?
    Your help is appreciated!
    regards,
    Peter

    Hi Peter,
    below is part of the mail i got from our basis person regarding the log file growing(i had to then switch the trace  off)...it is in the same directory as the file you are having...
    <i>"Disk space utilization for /usr/sap/XID on sapxid grew to 97% on Sunday and I found a very large log file in /usr/sap/XID/DVEBMGS61/work/ directory. It was still open so I had to stop XID before I could move it out of the files system. I put the file in /tmp/dev_server0.old."</i>
    Thanks,
    Renjith

  • 300 MB to 1.2 GB Forte log file automatically created

    General information
    ===================
    -One server: Windows NT 4.0 Server Enterprise Edition (service pack 6a), PC/x86, dual Pentium Pro 200 MHz.
    -Five workstations: Windows NT 4.0 Workstation (service pack 6a), PC/x86.
    -Forte 4GL 3.0.N.0.
    -SQL Server 7.0 (service pack 3), clustered.
    -Forte application partitioned into 1 server process (runs on server) and 1 client process (runs on all workstations).
    Has anyone seen this?...
    Problem description
    ===================
    About once per month, our Forte server partition log file grows to 300+ MB, and then the process crashes. This problem is not reproducible, and I don't yet know if there is any pattern in the sequence of events that leads to the error. All the log files appear to be similar because the traceback shows the same method.
    The error started happening after upgrading from Forte 3.0.G.2 to Forte 3.0.N.0.
    All of the client and server log files have the string "<unknown>" where the Forte environment name normally is. I believe that nodemgr.exe crashes, and usually it cannot be restarted. When the Forte Environment Manager is manually restarted, a Windows NT "Services" error window appears that says - "Could not start the Forte Environment Manager 3.0.N.0 service on \\SERVERA. Error 1067: The process terminated unexpectedly." Rebooting the server always recovers.
    Here is an example of the text extracted from one of the huge Forte log files...
    NOTE:
    -Some of the text lines may be wrapped (in the actual file, none of the lines are wrapped).
    -forte_ex_274.log was 263,119 KB.
    -The string "..." means that many lines are not included.
    -All hex values, except for addresses, have been changed to "0x00000000".
    -Note that "Page:45713 @ 0x02CA4400" is included, but appears to be empty.
    ********** BEGINNING OF FILE **********
    ftexec Forte Version 3.0.N.0
    Windows NT
    Forte Application Environment (tm), Forte Runtime Environment (tm),
    Forte Conductor (tm):
    Copyright (c) 1994-2000, Forte Software, Inc. and its licensors.
    US Patent No. 5,457,797
    Forte Express (tm), Forte WebEnterprise (tm):
    Copyright (c) 1994-2000, Forte Software, Inc.
    All Rights Reserved.
    Unpublished rights reserved under the copyright laws of the United States.
    Wed Oct 11 21:52:48 2000
    Process ID 274
    Attached to manager for node SERVERA.
    Loading partition IBIS_cl0_Part1 built on 23-Aug-2001 07:10:49.
    aud Sun Aug 26 05:45:17 : Loading partition IBIS_cl0_Part1 built on 23-Aug-2001
    07:10:49.
    Attached to manager for node SERVERA.
    ! Interpreter Traceback
    Traceback:
    IbisCommunicationHandler.ReadSocket at offset 268
    # Page 45713 contains Object 0x02CA4408 that has bad SIZE(0)
    # Scanning for value in range 0x2ca4400:0x2ca4410
    # Found 0x2ca4408 at qqin_ActivationRecord+0x28(0x2ca3bb8)
    ! Page:45713 @ 0x02CA4400 { Small Object Mobile  } Current
    # Page 45714 should be marked SPAN.
    # Page 45715 should be marked SPAN.
    # Page 45716 should be marked SPAN.
    # Page 45717 should be marked SPAN.
    # Page 45718 should be marked SPAN.
    # Page 45719 should be marked SPAN.
    # Page 45720 should be marked SPAN.
    # Page 45721 should be marked SPAN.
    # Page 45722 should be marked SPAN.
    # Page 45723 should be marked SPAN.
    # Page 45724 should be marked SPAN.
    # Page 45725 should be marked SPAN.
    # Page 45726 should be marked SPAN.
    # Page 45727 should be marked SPAN.
    # Page 45728 should be marked SPAN.
    # Page 45729 should be marked SPAN.
    # Page 45730 should be marked SPAN.
    # Page 45731 should be marked SPAN.
    # Page 45732 should be marked SPAN.
    # Page 45733 should be marked SPAN.
    # Page 45734 should be marked SPAN.
    # Page 45735 should be marked SPAN.
    # Page 45736 should be marked SPAN.
    # Page 81525 should be marked SPAN.
    # Page 81526 should be marked SPAN.
    # Page 81527 should be marked SPAN.
    # Page 81528 should be marked SPAN.
    # Page 81529 should be marked SPAN.
    # Page 81530 should be marked SPAN.
    # Page 81531 should be marked SPAN.
    # Page 81532 should be marked SPAN.
    # Page 81533 should be marked SPAN.
    # Page 81534 should be marked SPAN.
    # Page 81535 should be marked SPAN.
    ! Page:17536 @ 0x01120000 { Small Object Mobile  } Current
    ! 0x01120000: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120010: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120020: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120030: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120040: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120050: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120060: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120070: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120080: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120090: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011200F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120100: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120110: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120120: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120130: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120140: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120150: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120160: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120170: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120180: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120190: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011201F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120200: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120210: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120220: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120230: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120240: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120250: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120260: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120270: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120280: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120290: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011202F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120300: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120310: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120320: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120330: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120340: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120350: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120360: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120370: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120380: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120390: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011203F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! Page:17537 @ 0x01120400 { Small NonObject Mobile  } Current
    ! 0x01120400: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120410: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120420: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120430: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120440: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120450: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120460: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120470: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120480: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120490: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011204F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120500: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120510: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120520: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120530: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120540: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120550: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120560: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120570: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120580: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120590: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011205F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120600: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120610: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120620: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120630: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120640: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120650: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120660: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120670: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120680: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120690: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011206F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120700: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120710: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120720: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120730: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120740: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120750: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120760: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120770: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120780: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x01120790: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x011207F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! Page:17538 @ 0x01120800 { Large Object Mobile  } Current
    ! Page:45712 @ 0x02CA4000 { Small NonObject Mobile  } Current
    ! 0x02CA4000: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4010: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4020: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4030: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4040: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4050: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4060: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4070: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4080: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4090: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA40F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4100: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4110: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4120: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4130: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4140: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4150: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4160: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4170: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4180: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4190: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA41F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4200: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4210: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4220: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4230: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4240: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4250: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4260: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4270: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4280: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4290: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA42F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4300: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4310: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4320: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4330: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4340: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4350: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4360: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4370: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4380: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4390: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA43F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! Page:45713 @ 0x02CA4400 { Small Object Mobile  } Current
    ! Page:45714 @ 0x02CA4800 { Small Object Mobile  } Current
    ! 0x02CA4800: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4810: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4820: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4830: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4840: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4850: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4860: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4870: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4880: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4890: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA48F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4900: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4910: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4920: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4930: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4940: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4950: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4960: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4970: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4980: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA4990: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA49A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x02CA49B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F030: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F040: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F050: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F060: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F070: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F080: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F090: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0A0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0B0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0C0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0D0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0E0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F0F0: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F100: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F110: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F120: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F130: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F140: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F150: 0x00000000 0x00000000 0x00000000 0x00000000
    ! 0x0495F160: 0x00000000 0x00000000 0x00000000 0x00000000
    ********** END OF FILE **********

    This appears to the general output generated when a partition gets a SEGV or AccessViolation type problem. The runtime code always performs a memory check to determine if a possible cause for the problem was a memory corruption. In this case it thinks it found a problem and is attempting to dump information related to the problem. There was a bug in this routine that caused to dump more stuff than was really needed (I believe that this was fixed in 5.0)
    The actual error was someone wrote a 0 on the header of an object that describes the size of the object. Given that this was the first object on the page it could be a problem with someone overrunning the end of an object on the previous page.
    This can either be a runtime problem or an application problem. Its a little hard to tell from this output. The best way to collect more information would be to install MSDEV/Visual Studio on the machine and enable
    JustInTimeDebugging (this is normally enabled for you) and then add the following environment variable
    FORTE_NOHANDLER=yes
    This bypasses the exception handling and causes the MSDEV debugger to start. This should allow you to get a stack trace which will give more clues as to the problem.

  • What's wrong with the weblogic.log file?

    Currently we got a problem and don't know what it means -
    our weblogic.log file grows very fast by generating huge amount of logs like:
    ####<Feb 18, 2003 10:29:13 AM CST> <Info> <DGCserver> <awhq7232.whq.ual.com> <ECSserver>
    <ExecuteThread: '13' for queue: 'default'> <> <> <000000> <Tried to renew lease
    on lost reference: '1160'>
    I counted and found that weblogic.log adds in at least 50 such logs per minute
    and its size imcreases about 20M per day. But the application still work normally.
    Could you experts help us on the following questions:
    - Why WebLogic Container generates so many "Info" kind of logs?
    - Could we config the WebLogic Server to avoid such "Info" kind of logs being
    written into weblogic.log file?
    Thank you very much!
    Bill Yuan

    It is harmless - it means that by the time server got to process lease
    renewal message object is already gone.
    You may want to check with support - I think there was a fix which supressed
    this message.
    Bill Yuan <[email protected]> wrote:
    Currently we got a problem and don't know what it means -
    our weblogic.log file grows very fast by generating huge amount of logs like:
    ####<Feb 18, 2003 10:29:13 AM CST> <Info> <DGCserver> <awhq7232.whq.ual.com> <ECSserver>
    <ExecuteThread: '13' for queue: 'default'> <> <> <000000> <Tried to renew lease
    on lost reference: '1160'>
    I counted and found that weblogic.log adds in at least 50 such logs per minute
    and its size imcreases about 20M per day. But the application still work normally.
    Could you experts help us on the following questions:
    - Why WebLogic Container generates so many "Info" kind of logs?
    - Could we config the WebLogic Server to avoid such "Info" kind of logs being
    written into weblogic.log file?
    Thank you very much!
    Bill Yuan--
    Dimitri

  • Error in Log file

    I am wondering if anyone has ever seen errors like this. They started showing up in our log file recently with the error below. Once this error starts, then tons of errors are generated and the log file grows exponentially.
    2006-12-12 06:51:26,109 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=naap11//13513, BranchQual=] timed out. status=STATUS_ACTIVE
    2006-12-12 06:51:26,124 ERROR [org.jboss.ejb.plugins.LogInterceptor] TransactionRolledbackLocalException in method: public abstract com.adobe.pof.omapi.POFObjectSet com.adobe.pof.omapi.POFObjectManagerLocal.retrieveObjectSet(com.adobe.pof.omapi.POFQuery, int,int,com.adobe.idp.Context) throws com.adobe.pof.POFException, causedBy:
    org.jboss.util.NestedSQLException: Interrupted while requesting permit! Waited 0 ms; - nested throwable: (javax.resource.ResourceException: Interrupted while requesting permit! Waited 0 ms)
    Eventually, we get the following message:
    2006-12-12 06:51:30,622 WARN [org.jboss.ejb.plugins.jms.DLQHandler] Message resent too many times; sending it to DLQ; message id=ID:7-116593508609324
    2006-12-12 06:51:30,622 WARN [org.jboss.tm.TransactionImpl] Transaction TransactionImpl:XidImpl [FormatId=257, GlobalId=naap11//17644, BranchQual=] timed out. status=STATUS_ACTIVE
    2006-12-12 06:51:30,638 ERROR [org.jboss.ejb.plugins.jms.DLQHandler] Could not send message to Dead Letter Queue
    We are using LiveCycle 7.2 (WF, FM, FS and RES). Any ideas are welcome.

    where i should place my .cgi files folder in apllication context
    ....i am using jboss server

  • 903 management of app / out / err logs to rotating log files??

    I'm deploying BC4J apps under OC4J.
    One of my complaints about the production environment is that the noisy logging from
    BC4J is directed to a static file name by the shell startup script. This not enterprise nor
    manageable in a 24x7 environment since the log file grows boundlessly.
    It was mentioned that 903 OC4J would fix log mangement. I've not seen anymention in doc's.
    Might someone offer how -out and -err logs can be better managed in 903?
    Thanks curt

    To be 24/7 an appserver needs to at least support managing the System.out traffic
    that apps, frameworks (BC4J) spew.
    It was suggested that 903 OC4J will support rotating log files?
    Is this true and any help or doc pointers would be great.
    BTW, I'm moving to 903 enterprise with OEM.
    Thanks, curt Curt - there is no way in 903 to rotate log files for a specific OC4J instance.
    There is a feature request in place for this functionality but I am not sure which version it will be delivered with.
    -steve-

  • Log file becomes ridiculously massive

    The Windows system is Windows 7 32 bits
    SQL server is Microsoft SQL 2008 R2 express
    The database data file is around 120MB and the log file is 400GB
    The recovery model is simple
    Can anyone tell me what possible reasons are that caused log file becomes huge? Thank you in advance

    The Windows system is Windows 7 32 bits
    SQL server is Microsoft SQL 2008 R2 express
    The database data file is around 120MB and the log file is 400GB
    The recovery model is simple
    Can anyone tell me what possible reasons are that caused log file becomes huge? Thank you in advance
    there are various reasons for abnormal growth of your log file.
    try to figure out is there any open transaction in your database use - DBCC OPENTRAN
    also run this query
    select log_reuse_wait_desc from sys.databases where name = 'DATABASE_NAME'
    and analyze the result, this result will let you know possible reason for the log growth.
    Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    Praveen Dsa | MCITP - Database Administrator 2008 |
    My Blog | My Page

  • Log file shrinking

    hi every one
    i m very happy getting reply from u all
    here my doubt regarding log file shrink.in our environment all high avaliabilities are using (log shippimg,mirroring,replication) now my doubt is if i shrink log file of a database which is these H A what will be the reaction?does i ve to reconfigure or
    not?
    can i make snapshot database  for restoring database?
    waiting for replies with anxiety
    thanks&regards
    chetan.tk

    Hi chetan.kt,
    What is the purpose of shrinking log file? It is recommend that backup the log file frequently as a period of some minutes if the log file is large. In case of more space is required for operation in SQL Server, you may consider to increase the disk space.
    Befor shrinking, you should insight into the reason which leads to the log file grows unexpectedly: A transaction log grows unexpectedly or becomes full on a computer that is running SQL
    Server.
    For log shipping and database mirroring, you can shrink the log file on primary server with non-truncate, and the shrink operation will be log shipped to the secondary servers.
    As for replicated database, you cannot be able to shrink the log file if replication is not completed. You may have a try to mark all replicated transactions as completed by stopping log reader agent and restart after shrinking. For more information:
    Unable to shrink transaction log on replicated database - SQL 2008
    It is not a good idea to shrink the log file. You may have a look at Tibor’s blog about the problem of shrinking log file:
    Why you want to be restrictive with shrink of database files
    Best Regards,
    Stephanie Lv
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • [SOLVED]Log files getting LARGE

    I ran a pacman -Syu for the first time in several months yesterday, and my computer has become almost useless due the fact that everything.log, kernel.log and messages.log gets extremely large (3.8 GB) after a while, causing / to become 100% full.
    I've located the following in kernel.log:
    Mar 14 15:06:44 elvix attempt to access beyond end of device
    Mar 14 15:06:45 elvix attempt to access beyond end of device
    Mar 14 15:06:45 elvix sda5: rw=0, want=1812442544, limit=412115382
    Mar 14 15:06:45 elvix attempt to access beyond end of device
    Mar 14 15:06:45 elvix sda5: rw=0, want=1812442544, limit=412115382
    Mar 14 15:06:45 elvix attempt to access beyond end of device
    Not sure what it means, but the last two lines are repeated XX times and are the reason why log files grow beyond limits. Anyone got ideas to what can be done to fix this?
    Last edited by bistrototal (2008-03-14 16:27:15)

    logrotate works really well:
    http://www.archlinux.org/packages/14754/
    There's quite a few threads about configuration floating around.

  • How to limit the size of a log file.

    Hi,
    I am developing an application that creates a log file with all actions that take place. My problem is that this log file grows a lot because the application acts as a server that is up 24 hours a day. For that reason, I wanted to limit the size of the log file by deleting de older lines, how can implement is?
    Thanks.

    One way is to periodically (say every week) create a new file to store the actions and then, when the space taken up by all the files is too large, delete the oldest one.
    You can also have your application periodically (say the first time you write to the file on any calendar day) check the size of the file and, when it gets too big, copy all of the actions in the file after a given time (presumably there is an associated timestamp with each action) to a new file. Then delete the old file.

  • Stdout.log file

    My stdout.log file grows quite quickly (it's currently around 45MB and growing), however, because it's constantly in use it doesn't get rotated by my logrot process (I'm using LM3.2 on Windows 2003 Server).
    Is there a reason why this file grows quite quickly and is there a way to rotate it without stopping the Daemons, renaming the file, and then restarting the Daemons??
    If not, is there a maximum file I can let this file grow to without having to clear it?

    Thanks Joe...
    I stopped the Daemons and rotated the file on 23/12/09. The file is currently in excess of 75MB!!!
    I've attached the last couple of hundred lines of the log to see if that gives you any clues as I'm perplexed by this.
    Could there be a debug mode enabled somewhere in LMS?? I'm not sure which debug mode would write to the stdout.log file.
    As usual, any help greatfully received.

  • WebAnalyticsServiceApplication_ReportingDB log file and secondary DB files issue

    Hello everyone,
    So we have a problem, a customer has a SP2010 farm, SP on one server and SQL 2008r2 on another. Little (read none by the looks of things) maintenance has been applied to the server (both SQL and SP other than patching and windows backups) over nearly a year
    and we are here now to upgrade to SQL 2012, found the current state and the situation is as follows (up-to now):
    The SP install was done from the search server binaries to give better search options (thought this may be prudent to disclose)
    The WebAnalyticsServiceApplication_ReportingDB log file is HUGE and will not truncate, Ive done the following:
    backed up (full) the DB for web analytics  
    backed up log files for same DB (with truncate selected) (both through gui in SQL MS)
    Tried to shrink log file (this told me through the gui that 99% was free in the log file, but it freed up only 1%, even after trying again and selecting 'reorganise pages before releasing unused space' and selecting 0MB for the 'shrink to' size)
    Also, there are over 30 secondary DB files for this database, Ive seen other threads about these files but am stuck as how to do the following...
    no one uses the web analytics
    the data is not needed
    I understand it maybe needed in the future
    we do not need the data
    how should I get rid and stop future log file and secondary DB file growth? 
    Anyone's help would be greatly appreciated. 

    For reference, you can control how long SP keeps the Web analytics data (which does generate one extra .ndf per week).
    To set the limit on the data retention period:
    On the Central Administration Web site, in the Application Management section, click
    Manage service applications.
    Click the Web Analytics Service Application row to select it and in the
    Operations group of the ribbon click Properties.
    In the dialog box, in the Data Retention Period section, set the data retention period, which can range from 1 month to 25 months.
    See
    https://technet.microsoft.com/en-us/library/ee620541.aspx#section1 for more info

Maybe you are looking for