Message tracking max results returned
Hi All,
On message tracking page the predefined max rsults returned value only have 3 options 250, 500 and 1000. May i know how can i increase query setting more than 1000 results return.
Regards,
Rock
Hi Rock,
You cannot increase the query to more than 1000, but you can change your other parameters. For example, you could change the date scope until you get down to under 1000 results.
You will have to run multiple queries to pull all the data you're looking for, but unless/until they change the maximum results this will give you a workaround.
Thanks,
Rachel
Similar Messages
-
Max results returned by a search
Hi there,
I have been struggling in the Content DB Api to find out about the max results returned when performing a search.
Let's say for instance, I am doing a search on attribute NAME = * on a library that potentially contains more than 100 000 documents. I don't mind if the operation is time consuming or not, my main concern is the actual limit. I suppose this is certainly related
to the SOAP message limit. Does anyone know about this ?
I forgot to mention that the search won't request any attribute but only the defaults (id, name, type and so forth ...).
Cheers,Hi
i came across the below reply for a thread with the similar query as above.
<<
Justin Cave
Posts: 10,696
From: Michigan, USA
Registered: 10/11/99
Re: sort data in ref cursor
Posted: Feb 3, 2005 10:30 AM in response to: [email protected] Reply
No. You could sort the data in the SQL statement from which the REF CURSOR was created, but once you have a REF CURSOR, you cannot do anything but fetch from it.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC
>>
So, the results from a ref cursor cant be sorted?? There is no way out?
Kindly advise. -
Hi all,
I have TFS2012 and run several projects.
We encounterwed with such an error while using Build server.
Overall Build Process
Initial Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
00:00
Get the Build
00:00
Update Build Number
Initial Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Final Property Values
BuildNumberFormat = $(BuildDefinitionName)_$(Date:yyyyMMdd)$(Rev:.r)
Result = Ephone_DIT_Deploy_20150424.1
01:56
Run On Agent (reserved build agent U4VMDWODBDEV03 - Agent1)
Initial Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
00:00
Get the Build Directory
Initial Property Values
Result = d:\temp\217\CTI\Ephone_DIT_Deploy
01:53
If Not String.IsNullOrEmpty(ConfigurationFolderPath)
Initial Property Values
Condition = True
01:53
Run TfsBuild for Configuration Folder
Initial Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe /nologo /noconsolelogger "d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TFSBuild.proj" /m:1 /nr:False "@d:\temp\217\CTI\Ephone_DIT_Deploy\BuildType\TfsBuild.rsp"
00:08
Getting sources
00:02
Labeling sources
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileConfiguration.
00:19
Built $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT/TFSBuild.proj for target(s) CompileSolution.
00:19
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.sln for default targets.
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:10
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:05
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.EnterpriseServices.dll' targets a different processor
CSC: Assembly generation -- Referenced assembly 'System.Web.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:01
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Workflow.Targets (121): Compilation failed. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS/Communications.Protocol.CTIOS.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone.DelphiCallConn/Communications.Protocol.DelphiCallConn.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.Proxy/Communications.Protocol.Proxy.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.Workflow.Interface/EPhone.Workflow.Interface.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneReporting/EPhoneReporting.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Workflow/EPhone.Workflow.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallback/EPhoneCallback.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneMarcomApplication/EPhoneMarcomApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneCallbackApplication/EPhoneCallbackApplication.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneUserControl/EPhoneUserControl.csproj for default targets.
00:02
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneQueView/EPhoneQueView.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.DataModel.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1605): There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "d:\temp\217\CTI\Ephone_DIT_Deploy\Binaries\Debug\EPhone.dll",
"x86". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take
a dependency on references with a processor architecture that matches the targeted processor architecture of your project.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol/Communications.Protocol.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/CTIException/CTIException.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Protocol.CTIOS.TestRunner/Communications.Protocol.CTIOS.TestRunner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.CallGenerator/EPhone.Tests.CallGenerator.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests.Runner/Ephone.Tests.Runner.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Ephone.Tests/Ephone.Tests.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhoneIDD/EPhoneIDD.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/Communications.Softphone/Communications.Softphone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone.DataModel/EPhone.DataModel.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/EPhone/EPhone.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegratorTest/ChannelIntegratorTest.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/Common/Common.csproj for default targets.
00:00
Built $/CTI/DEV/DEV_INT/source/EPhone/Development/EPhone/ChannelIntegrator/ChannelIntegrator/ChannelIntegrator.csproj for default targets.
CSC: Assembly generation -- Referenced assembly 'System.Data.dll' targets a different processor
MSBuild Log File
00:08
Generating list of changesets
00:20
Built Skins\SkinEPhone.cs for default targets.
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
Skins\SkinEPhone.cs (3838): The member 'EPhone.SkinEPhone._txtOrderNumber_TextChanged(object, System.EventArgs)' does not hide an inherited member. The new keyword is not required. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneUserControl\EPhoneUserControl.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "microsoft.vbe.interop". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (3201): Unable to apply publish properties for item "stdole". [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (4513): Item 'Microsoft.Net.Framework.3.5' could not be located in 'C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\Bootstrapper\'. [d:\temp\217\CTI\Ephone_DIT_Deploy\Sources\EPhoneWinForm\EPhoneWinForm.csproj]
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\TeamBuild\Microsoft.TeamFoundation.Build.targets (1740): The "CreateNewWorkItem" task failed unexpectedly.
Microsoft.TeamFoundation.WorkItemTracking.Client.WorkItemTypeDeniedOrNotExistException: TF201077: The work item type Bug cannot be found. It may have been renamed or destroyed.
at System.Activities.WorkflowApplication.Invoke(Activity activity, IDictionary`2 inputs, WorkflowInstanceExtensionManager extensions, TimeSpan timeout)
at System.Activities.WorkflowInvoker.Invoke(Activity workflow, IDictionary`2 inputs, TimeSpan timeout, WorkflowInstanceExtensionManager extensions)
at Microsoft.TeamFoundation.Build.Tasks.WorkflowTask.ExecuteInternal()
at Microsoft.TeamFoundation.Build.Tasks.Task.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
00:03
Creating work item
Exception Message: TF270015: 'MSBuild.exe' returned an unexpected exit code. Expected '0'; actual '1'. See the build logs for more details. (type UnexpectedExitCodeException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Final Property Values
BinariesSubdirectory =
BuildDirectory = d:\temp\217\CTI\Ephone_DIT_Deploy
CommandLineArguments =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MaxProcesses = 1
NodeReuse = False
RecursionType = OneLevel
SourcesSubdirectory =
TargetsNotLogged =
TestResultsSubdirectory =
ToolPath =
ToolPlatform = Auto
Verbosity = Diagnostic
Final Property Values
Condition = True
Final Property Values
MaxExecutionTime = 00:00:00
MaxWaitTime = 04:00:00
ReservationSpec = Name=*, Tags=
Result = U4VMDWODBDEV03 - Agent1 (vstfs:///Build/Agent/217)
Final Property Values
AgentSettings = Use agent where Name=* and Tags is empty; Max Wait Time: 04:00:00
BinariesSubdirectory =
ConfigurationFolderPath = $/CTI/DEV/DEV_INT/source/TeamBuildTypes/EPhone_DIT
DoNotDownloadBuildType = False
LogFilePerProject = False
MSBuildArguments =
MSBuildPlatform = Auto
RecursionType = OneLevel
SourcesSubdirectory =
TestResultsSubdirectory =
Verbosity = Diagnostic
Please have a look and guide where to find a problem
Thanks aheadHi Hooi,
I'd like to know whether you can build successfully in your local machine with MSBuild. You have to build succeed with MSBuild beore you can build with TFS Build since TFS build use MSBuild as its default compiler.
From the error message, you might build with wrong platform for your project. Please check if the build platfrom is proper. If you have customization of your build process template, it would be better to elaborate the reproduce steps and customization details.
Best regards, -
Message class as result data object
hello brf+ users,
is it possible to use as Result data object in a Case expression a message from a custom message class?
thanks
danilothanks Carsten,
my requirement can be simplified in
IF FISCAL CODE
equals to " " then "001" ENTRY MISSING is returned
otherwise "000" check ok is returned.
where 000,001 are domain values of an element (MESSAGE RESULT).
can i use the message class as result? is there a way to anchor the result to the message class?
thanks
danilo -
OBIEE 11g - Customized Message for No result On all Reports
Hi,
The default messages displayed is getting displayed when a report returns no data in OBIEE 11g. I am aware of that, we can overide the default message with our Custom message at "Analysis" level. but it is very painful to do.
I am looking for a file where we can override the default messages with our custom message at one place.
Also, I have gone through the below link for this but it has change at the language level. I tried to change it at language "l_en" level but it did not work.
can anyone suggest for 11g?
http://obiee10grevisited.blogspot.com/2012/02/customized-message-for-no-result-on-all.html
Edited by: Nagen on May 6, 2013 4:36 PMHi Nagen,
Using a custom message should also work in 11g. Refer to this link for setting up custom messages in 11g.
http://www.rittmanmead.com/2010/12/oracle-bi-ee-11g-styles-skins-custom-xml-messages/
Thanks,
Gaurav -
Exchange Server 2010 - Message Tracking Logs - Log file creation
Hi,
I would like to find out on the behavior of the exchange server in the way that it logs the message tracking.
Currently the parameter used is
MessageTrackingLogMaxDirectorySize - 10GBMessageTrackingLogMaxAge - 30daysI would like to check when the Max Directory Size has exceeded the value indicated, does Exchange server immediately deletes the oldest log file to make space for the new logs?And in the event that the oldest file is being open or locked, will exchange server delete the next oldest file? or it will reattempt to delete the "locked" file for a period of time?Lastly, when these "oldest" files is not able to be deleted, will exchange server stops logging new tracking events?Thanks!Hi Zack,
Thank you for your question.
If you have configured the parameter of “MessageTrackingLogMaxDirectorySize” and “MessageTrackingLogMaxAge”, we think you have enable circular logging, it will delete the oldest message tracking log files for new log file when the either of the following
conditions is true:
The message tracking log directory reaches its specified maximum size.
A message tracking log file reaches its specified maximum age.
In addition, it didn’t exceeded the value indicated.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support -
current scenario exchange 2013 on premise.
our requirement is track the messages send from external domains (from internet)
We are using get-messagetrackinglog command and pipe it to test file.
below is command i am using
get-messagetrackinglog -sender "[email protected]" | fl > d:\user.txt
we not getting any output in the file.
please suggestHi,
From your description, I recommend you follow the steps below for troubleshooting:
1. Please check if you can see the message tracking log on the following folder:
C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\Logs\MessageTracking
2. If no, please restart the Microsoft Exchange Transport Log Search service and check the result.
What's more, here is a thread for your reference:
No Results for message tracking (Note: Though it is Exchange 2010, it is also useful in this issue)
http://social.technet.microsoft.com/Forums/exchange/en-US/8a9906e8-4d6a-4db6-b58e-1fee43dec4ce/no-results-for-message-tracking?forum=exchangesvradminlegacy
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support -
Message Tracking Center won't track messages
Hi Technet,
I'm using Exchange 2003 SP2. Tried to use message tracking center but it gives me the error:
" the search could not be completed. Check to see that the Microsoft Exchange Management service is running on all Exchange 2000 and Exchange 2003 installations."
Verified that
1. WMI service is running
2. Exchange managment is running
3. Exchange services running using Local system account
4. Under exchange services > properties > log on > interact with desktop is unchecked.
Looking at the message track log path, it contains the below error:
"An error occurred during a call to Windows Management Instrumentation
ID no: 80041013
Exchange System Manager"
Any tips on how I can enable the message tracking?I actually only have 1 exchange server. So there isn't any for me to compare :P lol.
Anyway. The WMI control settings for ROOT\WMI :
Administrators
all permission allowed, except for special permissions
Everyone, Local Service and Network Service
Allowed execute methods, Provider Write, Enable Account.
================
The message track log path becomes normal when the server is rebooted, but after a few moments it will return to the error
"An error occurred during a call to Windows Management Instrumentation
ID no: 80041013
Exchange System Manager"
And in event vwr application log, we can see this event
=====================
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 5007
Date: 04/02/2010
Time: 8:56:11 AM
User: N/A
Computer: MYKLX001
Description:
An error occurred during the message tracking decode operation. error from file: f:\tisp2\admin\src\libs\rpc\rwlog.cxx line: 517. <<0xc0070842 - The Server service is not started.>>
=====================
I have verified that the message tracking log share is there via "net share"
Is this a problem with the WMI control permission? -
We installed a C150 in our office and we enabled Message tracking on the day we installed the device. However when we try to find messages all the way back to October (the 13th, the day we installed it) there were no results found. At the top of the message tracking page we have this:
Available Time Range: 13 Oct 2008 15:04 to 23 Dec 2008 12:50 (GMT -0500)
Data in time range: 99.98% complete
Is there any way we can track messages back that far?
I do have a support case open, but I wanted to see if anyone else has that issue.The following article is in the knowledge base:
Earliest 15% of Tracking Data Is Not Currently Available for Querying
Question
Why does the "Available Time Range" appear to be missing the oldest data?
Answer
This is a known centralized message tracking issue in which the earliest 15% of tracking data is not currently available for querying. However, the appliance retains the data, and the data will be available for querying after this issue has been resolved.
A future release will provide access to 100% of the time range in the tracker database.
This is Defect ID 39471.
Hope this will explain your problems (the only way to find the missing part is via the CLI-find/grep command).
Peter -
Seeburger message tracking archiving / deleting question
Hello,
We are using Seeburger 1.7 with XI 7.0 for our EDI translations..We store information in Seeburger Message Tracking for our business requirements.I would like to know how these entries could be archived(Compressed) and stored or deleted after certain days so that we wont max up our storage..?
Any suggestions are appreciated.
Thanks in advance!
LarryPrateek,
Thanks for your response.Yes,I could find the "Archive Configuration" option..when I click that it shows me a screen saying show master data with two items with check boxes (Document Types & Archiving Systems)..On clicking the details of them I see set of parameters which shows the profile and the document type..not sure how to proceed from here to set up any archiving / deletion..any help is appreciated..
Regards,
Larry. -
Nautilus does not show Tracker search results
Hi,
I recently installed tracker and had it index my files. After indexing had finished, I tried tracker-search and tracker-needle, both of which returned the files I was looking for. But in Nautilus, searching via CTRL+F still only returns files whose filenames are matching my query. Nautilus does not seem to integrate Tracker search results properly, as it should according to this forum thread. Tagging files via the tracker-tags plugin in Nautilus works just fine. Re-installing nautilus did not change anything.
Any ideas what could be the problem here?
Thanks,
mfsHmm, I think it is supposed to use tracker if installed. At least nautilus has a build option called enable-tracker which is set to auto by default (I also compiled it with enable-tracker=yes but nothing changed). Also, "wonder" said in the thread quoted above that nautilus would use tracker and find only as fallback.
Last edited by mfs (2012-03-06 22:27:09) -
How to limit the number of search results returned by oracle text
Hello All,
I am running an oracle text search which returned the following error to my java program.
ORA-20000: Oracle Text error:
DRG-51030: wildcard query expansion resulted in too many terms
#### ORA-29902: Fehler bei der Ausführung von Routine ODCIIndexStart()
ORA-20000: Oracle Text error:
DRG-51030: wildcard query expansion resulted in too many terms
java.sql.SQLException: ORA-29902: Fehler bei der Ausführung von Routine ODCIIndexStart()
ORA-20000: Oracle Text error:
DRG-51030: wildcard query expansion resulted in too many terms
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169)
When i looked up the net, one suggestion that was given is to narrow the wildcard query, which i cannot in my search page. Hence I am left with the only alternative of limiting the number of results returned by oracle text search query.
Please let me know how to limit the number of search results returned by oracle text so that this error can be avoided.
Thanks in advance
krkHi,
If not set explicitly, the default value for WILDCARD_MAXTERMS is 5000. This is set as a wordlist preference. This means that if your wildcard query matches more than 5000 terms the message is returned. Exceeding that would give the user a lot to sift through.
My suggestion: trap the error and return a meaningful message to the user indicating that the search needs to be refined. Although it is possible to increase the number of terms before hitting maxterms (increase wildcard_maxterms preference value for your wordlist), 5000 records is generally too much for a user to deal with anyway. The search is not a good one since it is not restricting rows adequately. If it happens frequently, get the query log and see the terms that are being searched that generate this message. It may be necessary to add one or more words to a stoplist if they are too generic.
Example: The word mortgage might be a great search term for a local business directory. It might be a terrible search term for a national directory of mortgage lenders though (since 99% of them have the term in their name). In the case of the national directory, that term would be a candidate for inclusion in the stoplist.
Also remember that full terms do not need a wildcard. Search for "car %" is not necessary and will give you the error you mentioned. A search for "car" will yield the results you need even if it is only part of a bigger sentence because everything is based on the token. You may already know all of this, but without an example query I figured I'd mention it to be sure.
As for limiting the results - the best way to do that is to allow the user to limit the results through their query. This will ensure accurate and more meaningful results for them.
-Ron -
Cannot locate client IP Addess in message tracking logs
Hello
Im having trouble with a client who has an Exchange 2010 environment. They wish to identify users (via their client IP addresses of their workstations) who may be sending a large number of emails.
In this environment there are two CAS servers that are hardware load balanced.
My client wishes to interrogate the Message tracking logs (I believe this is the right place) in order to identify the IP address of a client which sent the originating mails. However the message tracking logs returns only the address of the Load Balancer
and not the client IP Address of the sending machine.
Is this anyway this can resolved?
Many thanks in advanceHi,
Or we can use
IIS Advanced Logging. Add field “X-Forwarded-For” to the Advance Logging configuration to find the real IP address of the client device. Here are steps.
Install “Advanced Logging” on each CAS server: Double click on msi file. Check the accept checkbox and click, next, next and finish for the installation.
Add field “X-Forwarded-For” to the Advance Logging configuration.
From your Windows Server 2008 or Windows Server 2008 R2 device, open the Internet Information Services (IIS) Manager.
From the Connections navigation pane, click the appropriate CAS or CHM server on which you are configuring Advanced Logging. The Home page appears in the main panel.
From the Home page, under IIS, double-click Advanced Logging.
From the Actions pane on the right, click Edit Logging Fields.
From the Edit Logging Fields dialog box, click the Add Field button, and then complete the following:
In the Field ID box, type X-Forwarded-For.
From the Category list, select Default.
From the Source Type list, select Request Header.
In the Source Name box, type X-Forwarded-For.
Click the OK button in the Add Logging Field box, and then click the OK button in the Edit Logging Fields box.
Click a Log Definition to select it. By default, there is only one: %COMPUTERNAME%-Server. The log definition you select must have a status of Enabled.
From the Actions pane on the right, click Edit Log Definition or right click and select Edit Log Definition.
Click the Select Fields button, and then check the box for the X-Forwarded-For logging field.
Click the OK button.
From the Actions pane, click Apply.
Click Return To Advanced Logging.
In the Actions pane, click Enable Advanced Logging.
Now, when you look at Inetpublogs, you will see a new AdvancedLogs folder will be available with new logs and these logs will have the client device IP address.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support -
Ironport Message Tracking Logs
Hi,
Am unable to post this in the Ironport Security section due to the restricted access on my Cisco support login ID.
I need to export the message tracking logs for a particular user for the last one year (or the period for which logs are available) on Ironport M660.
The GUI only reports 250 search results for every search and I have approx to export logs for approx. 20,000 messages.
Is there a Unix/CLI command which can be executed to export all tracking logs between a time frame in Ironport?
Thanks.This was a defect covered in the 8.5.6-093 release:
http://www.cisco.com/c/dam/en/us/td/docs/security/esa/esa8-5-6/ESA_8-5-6_HP1_Release_Notes.pdf
So, if running the -074 revision... found defect:
https://tools.cisco.com/bugsearch/bug/CSCuq49620
I wouldn't say that running repengupdate force is not suppose to be done, aside from a formal request... is odd to see or hear that would have been mentioned. With the force updates for any of the processes on the ESA, this is usually always a good troubleshooting step for any customer --- as the process will instantly call out to the updater servers, compare manifests, and then pull regardless of what is running the latest engine and rules sets for the process... and then silently implement in the background. While for the customers who might have bandwidth limiting options running on their network, the only major side effect is the package size that is coming across... since the engine is tagged into the rules...
But, normally with antivirus and antispam - this is the most helpful to run antivirusupdate force or antispamupdate ironport force. Especially in times where the update process itself may have been interrupted with a network related hiccup or staled out download.
-Robert -
BatchUpdateException :Results returned for UPDATE ONLY.
I got an error message at the statement stmt.executeBatch();
java.sql.BatchUpdateException: Results returned for UPDATE ONLY.
There are 3 SQL commands in the batch and it throws the above exception while executing the first command.
(The first command is a SELECT command with COUNT returned to a variable
eg. SELECT @ABC := COUNT(*) ....
The second and the third commands use the returned variable to make updates)
I printed out the updated information using BatchUpdateException.getUpdateCounts and I got
-3 1 1 (-3 means Statement.EXECUTE_FAILED)
However, I checked the database (mysql) and I discovered those two update commands were executed correctly ???!!!
An interesting thing is: if I use stmt.execute or stmt.executeQuery instead of executeBatch, it works fine and doesn't throw any exception.
I wonder if anybody experience similar situation before or have idea on this problem. Thanx :)Can somebody help me, please?
Maybe you are looking for
-
How to Upload a RTF Template from desktop with out using XML Publisher resp
Dear All, While uploading an RTF template for an XML report through XML Admin responsiblity, i am getting some weird error. So, i am looking for other options of uploading the Template. Can any one let me know if any other options are available. Can
-
Old codec no longer works with update to 7.1.3
The previous version of Quicktime 7 worked fine with an older codec (Accom Affinity) but now this newest version of Quicktime does not. Is there a way to go back to the earlier version of Quicktime 7 without having to reinstall all the system softwar
-
Error Code: 86000108 - New Lumia 640
Can someone advise on this recurrent problem? I cannot sync with hotmail.com - no email, contacts or calenders on a new Lumia 640. I cannot figure it out. I have tried to reset the phone, clicked and unclicked sync email and performed multiple har
-
IPhoto 11 will not open, I tried reloading my ILife but that did not work either. It says the certificate expired Mar 23, 2012
-
Is there a way to calculate the area of a shape?
I work in toy packaging and the size of the warning we have to use is dictated by the size of the package. On most items, it's pretty straight forward, LxW... But that doesn't always work, as the packaging isn't always that simple. Is there a way to