Exchange 2013 BPA results???
I have 3 new exchange 2013 physical servers, all 3 return this BPA critical error, see below - doesn't make sense.
Hi，
About the error message under the BPA, I found some information for your reference:
IIS uses application pools to separate Web applications and Web sites. Each application pool is served by a worker process or by a set of worker processes. Each worker process operates as a separate instance. The worker process for one application pool
is separate from worker processes for other application pools.
More details in the following article:
An application pool is running under an incorrect identity
http://technet.microsoft.com/en-us/library/dd535385(v=exchg.80).aspx
Even though the Exchange Version is Exchange 2007, hope the method is helpful.
Thanks
Mavis
Mavis Huang
TechNet Community Support
Similar Messages
-
BPA for Exchange 2013 still in beta!?
Exchange 2013 is over 2 years old.
Is Microsoft ever going to release a BPA for their flagship messaging platform that's NOT in beta?Hi,
At present, there is only a beta of Best Practices Analyzer for Exchange 2013 available. If you want to get the latest information about it, please pay attention to the Exchange blog.
For your convenience:
http://blogs.technet.com/b/exchange/
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support -
Exchange 2013 Untrusted Cross-Forest Availability Intermittently Working
Goal:
I’m attempting to configure cross-forest availability for Exchange 2013 using the instructions here:
http://technet.microsoft.com/en-us/library/bb125182%28v=exchg.150%29.aspx
At the very bottom of the page are three different methods. I have tried the first (per-user) and the third (untrusted) methods, with identical results. For various unfortunate reasons, I am unable to use the Microsoft Federated Gateway for availability
information (although that is configured in the production domain and I would use it if it were possible).
Situation:
When attempting to view availability information in either OWA or Outlook, the free/busy information typically isn’t visible. If you open and close Outlook a few times, creating meetings with the users in other domains, sometimes the other user’s information
will be visible, and sometimes it will not. When it is not, the area is filled with diagonal lines and hovering over it says “No Information”. The situation is the same in both Adatum trying to access Contoso, and in Contoso trying to access either
Adatum or Fabrikam.
I’m currently close to finishing up my third week with Microsoft Support on this issue, and am starting over with a third first level support person. They are quickly eroding what little confidence I had in them already. I’m posting here because
I’m desperate, and web searches for my errors turn up zero results. I fear this method of availability sharing doesn’t actually work correctly in Exchange 2013 as Microsoft is pushing organizations to use the Microsoft Federated Gateway, but I’d love
to heave about anyone getting this to work, or not.
Setup:
There are three separate domains I am working with (names changed to protect the innocent). Contoso.local is the production domain, containing Exchange 2007 and Exchange 2013 SP1 servers. Adatum.local is a test domain set up fresh with Exchange
2013 SP1. Fabrikam.com is a remote Exchange system that I others are connecting to without issue using Exchange 2010.
The Contoso and Adatum domain controllers are running Windows Server 2008 R2 SP1 and are running at a 2008 R2 functional levels. The Exchange 2013 servers are all at SP1 (results were the same prior to SP1), and the OS is Windows Server 2012.
Contoso has two sites, connected via 10Gbps links, and ~10ms latency, with Exchange 2013 CAS and mailbox servers in both sites. Adatum has a single site, and has two CAS and two mailbox servers. Fabrikam has one internet facing server to connect
to. A handful of contacts have been created in both Contoso and Adatum for the other domains, to select to view availability.
Contoso and Adatum domains sit on different subnets, but there is no firewall or filtering between their subnets. Routing between them is completely unimpeded. The Fabrikam server sits on another network across the internet, but firewalls have
been configured and I can browse the availability website from the Contoso CAS servers.
The CAS servers were originally set up to be load balanced, but working with Microsoft they’ve had me specify a single CAS server for autodiscover/EWS/ECP/OWA/etc in both Contoso and Adatum. The number of actual users on Exchange 2013 in Contoso is
~10. In Adatum, there are only a handful of mailboxes configured. The Exchange 2007 servers in Contoso are using Public Folders for free/busy replication for other domains right now, and we don’t care at the moment if they can use the 2013 availability.
None of our testing/configurations have involved the Exchange 2007 servers. There are no SPNs configured for the other domains in AD.
Errors:
There are three basic errors that are returned in Outlook diagnostics. The first is the timeout error. For a given mailbox server, the first time it is queried for availability information for a remote domain (after some amount of time of being
idle) it might not respond for 70 seconds (actually somewhere between 69 and 70 seconds each time when viewing the IIS logs), and eventually fails with the timeout error. If it doesn’t timeout, then it will respond with the Correct Response.
Once a particular mailbox server has timed out, it will typically immediately return the first Availability Error for all subsequent calls. Less frequently, it will return Availability Error 2. If a mailbox server returns the first Availability
Error, then it will continue to return that error until it times out again or starts working. Similarly, if a mailbox server returns the second Availability Error, then it will continue to return that error until it times out again or starts working.
If an IISRESET is performed on a mailbox server, then it will either timeout at the next cross-forest availability request, or work. There is never an issue accessing availability information for users in the same domain as the request.
If the remote Exchange is in an errored state, then the response includes the error. For example, if the mailbox servers in the remote domain are turned off, and the local mailbox server that you are querying happens to be responding correctly
for the remote domain, then it will return an error about how no mailbox servers are available in adatum.local to service the request.
There are no Event Log errors that correspond to failed requests of any type. IIS logs don’t show anything beyond what is shown in the Outlook diagnostics. There are no DNS or Active Directory Replication errors in the Event Logs.
Timeout error:
CalendarEvents : {}
ViewType : None
MergedFreeBusyStatus : {}
WorkingHours :
Result : Error
ErrorCode : ErrorTimeoutExpired
ErrorMessage : Microsoft.Exchange.InfoWorker.Common.Availability.TimeoutExpiredException: Request could not be processed in time. Timeout occurred during 'LookupRecipientsBatchBegin'.
. Name of the server where exception originated: Mailbox01
ErrorDetails : {}
ErrorProperties : {}
Availability Error:
CalendarEvents : {}
ViewType : None
MergedFreeBusyStatus : {}
WorkingHours :
Result : Error
ErrorCode : ErrorProxyRequestProcessingFailed
ErrorMessage : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AutoDiscoverFailedException:
AvailabilityAddressSpace 'adatum.local' couldn't be used because the Autodiscover endpoint couldn't be discovered.
. Name of the server where exception originated: Mailbox01
ErrorDetails : {}
ErrorProperties : {}
Availability Error 2:
CalendarEvents : {}
ViewType : None
MergedFreeBusyStatus : {}
WorkingHours :
Result : Error
ErrorCode : ErrorProxyRequestProcessingFailed
ErrorMessage : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AddressSpaceNotFoundException:
Configuration information for forest/domain swelab.wayad.corp.wayport.net could not be found in Active Directory.
at Microsoft.Exchange.InfoWorker.Common.Availability.TargetForestConfigurationCache.FindByDomain(OrganizationId
organizationId, String domainName)
at Microsoft.Exchange.InfoWorker.Common.Availability.QueryGenerator.GetTargetForestConfiguration(EmailAddress
emailAddress)
. Name of the server where exception originated: Mailbox02
ErrorDetails : {}
ErrorProperties : {}
Working:
CalendarEvents : {Microsoft.Exchange.WebServices.Data.CalendarEvent}
ViewType : FreeBusyMerged
MergedFreeBusyStatus : {Free, Free, Free, Free...}
WorkingHours : Microsoft.Exchange.WebServices.Data.WorkingHours
Result : Success
ErrorCode : NoError
ErrorMessage :
ErrorDetails : {}
ErrorProperties : {}
Start : 04/09/2014 00:00:00
End : 04/12/2014 00:00:00
Subject :
Location :
Testing Methodologies:
While it is possible to dig through Outlook diagnostics and OWA, we ended up scripting out these requests to save time. Microsoft support refuses to use the scripts, but they produce the same output that it takes them days to find in the logs, so I’ll
post them here to help anyone in the future.
Through reading the documentation and experimenting, it appears that the Exchange 2013 CAS servers really do just proxy availability requests from the client to the mailbox servers. At least by default, it seems to pick a mailbox server in the same
site, but which mailbox server in the site appears to be random. It will typically pick the same one repeatedly for a while.
The first script uses the Microsoft Exchange Web Services Managed API 2.1.
http://www.microsoft.com/en-us/download/details.aspx?id=42022
You specify a source email address, and a target address in the remote domain, and it creates a SOAP request that it sends to a CAS server of the source email address. The CAS proxies the request to the mailbox server which either responds with a failure
or the free/busy data.
The second script takes the XML SOAP request generated by the first script, and uses that to query a mailbox server directly. That allows you to test specific mailbox servers that are working or failing, instead of randomly using whichever mailbox
server the CAS happens to select. I generated a SOAP request with the first script that I knew had some data, and then copy/pasted it into the second script to verify if data was being returned.
I’ve deleted and recreated the availability address spaces in Contoso and Adatum for each other and Fabrikam multiple times. I’ve reset the password in the OrgWideAccount in both Adatum and Contoso, and viewed the lastBadPassword attribute in both
ADs to verify it wasn’t failing authentication. (A failed authentication also generates a 401 error that is returned to the client.) I can access the availability site of the other domain using the credentials of the OrgWideAccount without any
errors ever.
First Script:
# Import the Exchange Web Services module
Import-Module -Name "C:\Program Files (x86)\Microsoft\Exchange\Web Services\2.1\Microsoft.Exchange.WebServices.dll"
# Create the services object used to connect to Exchange
# You can specify a specific Exchange version, which I had to do to connect to 2007
# Exchange2007_SP1
# Exchange2010
# Exchange2010_SP1
# Exchange2010_SP2
# Exchange2013
# $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1
# $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
$Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService
$Service.UseDefaultCredentials = $true
# Specify an SMTP address. The autodiscover URL from the associated mailbox will be used to connect to Exchange
# This is used to distinguish resolving from the 2007 server versus 2013
#$Service.AutodiscoverUrl("[email protected]") # For Exchange 2007
$Service.AutodiscoverUrl("[email protected]") # For Exchange 2013
# Increase the amount output at the end to include the SOAP commands
$Service.TraceEnabled = $true
# Specify time frame to get free/busy for
$StartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"))
$EndTime = $StartTime.AddDays(7)
# Create the various objects needed to perform the EWS request
$drDuration = new-object Microsoft.Exchange.WebServices.Data.TimeWindow($StartTime,$EndTime)
$AvailabilityOptions = new-object Microsoft.Exchange.WebServices.Data.AvailabilityOptions
$AvailabilityOptions.RequestedFreeBusyView = [Microsoft.Exchange.WebServices.Data.FreeBusyViewType]::DetailedMerged
$Attendeesbatch = New-Object "System.Collections.Generic.List[Microsoft.Exchange.WebServices.Data.AttendeeInfo]"
$attendee = New-Object Microsoft.Exchange.WebServices.Data.AttendeeInfo($userSMTPAddress)
# Specify SMTP addresses of accounts to request availability for
#$Attendeesbatch.Add("[email protected]")
$Attendeesbatch.Add("[email protected]")
#$Attendeesbatch.Add("[email protected]")
#$Attendeesbatch.Add("[email protected]")
# Clear out old results so that a failed request doesn't show information still
$availresponse = ""
# Request the availability information from Exchange
$availresponse = $service.GetUserAvailability($Attendeesbatch,$drDuration,[Microsoft.Exchange.WebServices.Data.AvailabilityData]::FreeBusy,$AvailabilityOptions)
# Show summary information that would include errors
$availresponse.AttendeesAvailability
# Show all of the appointments in the requested time period
foreach($avail in $availresponse.AttendeesAvailability){
foreach($cvtEnt in $avail.CalendarEvents){
"Start : " + $cvtEnt.StartTime
"End : " + $cvtEnt.EndTime
"Subject : " + $cvtEnt.Details.Subject
"Location : " + $cvtEnt.Details.Location
Second Script:
# Change the server in this URL to specify which mailbox server to access
$url = 'https://mailbox01.contoso.local:444/EWS/Exchange.asmx'
# Uncomment the below lines if you want to query EWS using credentials other than
# the ones used to run the script.
#If(!(Test-Path variable:global:cred))
# $cred = Get-Credential
function Execute-SOAPRequest
[Xml] $SOAPRequest,
[String] $URL
write-host "Sending SOAP Request To Server: $URL"
$soapWebRequest = [System.Net.WebRequest]::Create($URL)
# These appear to be the only things needed in the headers when making the request
$soapWebRequest.ContentType = 'text/xml;charset="utf-8"'
$soapWebRequest.Accept = "text/xml"
$soapWebRequest.Method = "POST"
If(Test-Path variable:global:cred)
$soapWebRequest.Credentials = $cred
Else
$soapWebRequest.UseDefaultCredentials = $true
write-host "Initiating Send."
$requestStream = $soapWebRequest.GetRequestStream()
$SOAPRequest.Save($requestStream)
$requestStream.Close()
write-host "Send Complete, Waiting For Response."
$resp = $soapWebRequest.GetResponse()
$responseStream = $resp.GetResponseStream()
$soapReader = [System.IO.StreamReader]($responseStream)
$ReturnXml = [Xml] $soapReader.ReadToEnd()
$responseStream.Close()
write-host "Response Received."
return $ReturnXml
# The specing and line returns in the below variable are important for some reason
# For example, there must be a line return after the @' on the first line, or it's invalid...
# Change the line with this:
# <t:Address>[email protected]</t:Address>
# to the email address in the domain you want to query
$soap = [xml]@'
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<t:RequestServerVersion Version="Exchange2013_SP1" />
<t:TimeZoneContext>
<t:TimeZoneDefinition Name="(UTC-06:00) Central Time (US & Canada)" Id="Central Standard Time">
<t:Periods>
<t:Period Bias="P0DT6H0M0.0S" Name="Standard" Id="Std" />
<t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/1" />
<t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/2007" />
</t:Periods>
<t:TransitionsGroups>
<t:TransitionsGroup Id="0">
<t:RecurringDayTransition>
<t:To Kind="Period">Dlt/1</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>4</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>1</t:Occurrence>
</t:RecurringDayTransition>
<t:RecurringDayTransition>
<t:To Kind="Period">Std</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>10</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>-1</t:Occurrence>
</t:RecurringDayTransition>
</t:TransitionsGroup>
<t:TransitionsGroup Id="1">
<t:RecurringDayTransition>
<t:To Kind="Period">Dlt/2007</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>3</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>2</t:Occurrence>
</t:RecurringDayTransition>
<t:RecurringDayTransition>
<t:To Kind="Period">Std</t:To>
<t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
<t:Month>11</t:Month>
<t:DayOfWeek>Sunday</t:DayOfWeek>
<t:Occurrence>1</t:Occurrence>
</t:RecurringDayTransition>
</t:TransitionsGroup>
</t:TransitionsGroups>
<t:Transitions>
<t:Transition>
<t:To Kind="Group">0</t:To>
</t:Transition>
<t:AbsoluteDateTransition>
<t:To Kind="Group">1</t:To>
<t:DateTime>2007-01-01T06:00:00.000Z</t:DateTime>
</t:AbsoluteDateTransition>
</t:Transitions>
</t:TimeZoneDefinition>
</t:TimeZoneContext>
</soap:Header>
<soap:Body>
<m:GetUserAvailabilityRequest>
<m:MailboxDataArray>
<t:MailboxData>
<t:Email>
<t:Address>[email protected]</t:Address>
</t:Email>
<t:AttendeeType>Required</t:AttendeeType>
<t:ExcludeConflicts>false</t:ExcludeConflicts>
</t:MailboxData>
</m:MailboxDataArray>
<t:FreeBusyViewOptions>
<t:TimeWindow>
<t:StartTime>2014-04-03T00:00:00</t:StartTime>
<t:EndTime>2014-04-10T00:00:00</t:EndTime>
</t:TimeWindow>
<t:MergedFreeBusyIntervalInMinutes>30</t:MergedFreeBusyIntervalInMinutes>
<t:RequestedView>DetailedMerged</t:RequestedView>
</t:FreeBusyViewOptions>
</m:GetUserAvailabilityRequest>
</soap:Body>
</soap:Envelope>
$ret = Execute-SOAPRequest $soap $url
# Uncomment out one of the below two lines to get output in different alternative formats
#$ret | Export-Clixml c:\temp\1.xml;Get-Content c:\temp\1.xml
#$ret.InnerXml
# If the request is successful, show the appointments, otherwise show the failure message
If ($ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage.ResponseClass -eq 'Success')
$ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.FreeBusyView.CalendarEventArray.CalendarEvent
Else
$ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessageIn this case, the SMTP domain is the same as the AD domain. If the wrong domain were configured then the connection would never work, as opposed to sometimes work.
RunspaceId : abb30c12-c578-4770-987f-41fe6206a463
ForestName : adatum.local
UserName : adatum\availtest
UseServiceAccount : False
AccessMethod : OrgWideFB
ProxyUrl :
TargetAutodiscoverEpr :
ParentPathId : CN=Availability Configuration
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : adatum.local
DistinguishedName : CN=adatum.local,CN=Availability Configuration,CN=Wayport,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local
Identity : adatum.local
Guid : 3e0ebc2c-0ebc-4be8-83d2-077746180d66
ObjectCategory : contoso.local/Configuration/Schema/ms-Exch-Availability-Address-Space
ObjectClass : {top, msExchAvailabilityAddressSpace}
WhenChanged : 4/15/2014 12:33:53 PM
WhenCreated : 4/15/2014 12:33:35 PM
WhenChangedUTC : 4/15/2014 5:33:53 PM
WhenCreatedUTC : 4/15/2014 5:33:35 PM
OrganizationId :
OriginatingServer : dc01.contoso.local
IsValid : True
ObjectState : Unchanged -
Move mailboxes and public folders from exchange 2007 to Exchange 2013
1. How do i move mailboxes from exchange 2007 to exchange 2013. I have more than 1000 mailboxes.
What is the correct way to migrate. do i need to move a single mailbox. During migration do the mailboxes get corrupted
2. I want to move public folders from Exchange 2007 to Exchange 2013.
I ran powershell commands and got these results please do guide me how to move to exchange 2013.and what are the shell commands
Get-publicfolder
Name Parent Path
IPM_SUBTREE
Get-publicfolder | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
Get-PublicFolderStatistics | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
exchangeV1 schema-root\microsoft\exchangeV1
Internet Newsgroups Internet Newsgroups
Get-PublicFolder -Recurse | fl name,replicas > c:\publicfolder.txt
Name : IPM_SUBTREE
Replicas : {}
Name : Internet Newsgroups
Replicas : {MAIL\Public Folder Storage\Public Folder Database}I have started moving mailboxes , i have tried moving few individual mailboxes to see how things go
MAIL is my exchange 2007 and MAIL1 is my exchange 2013, please do refer the below result
PS] C:\Windows\system32>Get-MailboxDatabase -server mail
Name Server Recovery
ReplicationType
Mailbox Database MAIL False None
[PS] C:\Windows\system32>Get-MailboxDatabase -server mail1
Name Server Recovery
ReplicationType
Mailbox Database 1460777952 MAIL1 False None
[PS] C:\Windows\system32>New-MoveRequest -Identity '[email protected]' -TargetDatabase "Mailbox Database 1460777952"
DisplayName StatusDetail TotalMailboxSize
TotalArchiveSize PercentComplete
[email protected] Queued 363.6 MB (381,217,115 ...
0 -
Recreation of user mailbox from exchange 2007 to Exchange 2013
In my domain I was using Exchange 2007 earlier. I have installed Exchange 2013 successfully and running perfectly. I have one Issue:
1. A user's mailbox in Exchange 2007 was disabled from Exchange 2007 and recreated on Exchange 2013.
When a user try to send mail from outlook be it old one(2007) or new exchange(2013), gets NDR
If user send via owa it get delivered.
2. External mails are coming and user can send also like gmail or yahoo.
This is not an issue of cached address (outlook) I have checked this possibility.
Any luck
Deepak Vashistha
Deepak Vashistha Network Admin. Mayo College AjmerHi,
From your description, OWA works well, the issue is related to Outlook side. In your case, I recommend you update the Address Book manually on Outlook and check the result. If the issue persists, you need to re-create the profile.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support -
Help With Migration From Exchange 2007 To Exchange 2013
We have an Exchange 2007 Server with Service Pack 3 and Rollup 12 applied.
I installed a new Exchange 2013 Server and then immediately applied CU3.
I am following this Technet article:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The only deviation from the instruction I have had to do is in Part 2, section 4 “Configure offline address book (OAB)”.
Instead of entering:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2013)"
I had to enter:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2012)"
I believe this is due to the fact that the writer installed from an Exchange 2013 CU1 disk and I only had Exchange 2013.
Also when I tried to run:
Move-OfflineAddressBook -Identity "Default Offline Address Book" -Server SRV-EX2013
I get the following error:
Move-OfflineAddressBook : Failed to create the 'ExchangeOAB' folder on the target server 'SRV-EX2013'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform
this operation. Error message : 'Catastrophic failure (Exception from RESULT: 0x8000FFFF (E_UNEXPECTED))'.At line:1 char:24+ Move-OfflineAddressBook <<<<
-Identity "Default Offline Address Book" -Server SRV-ex2013+ CategoryInfo
: InvalidResult: (Default Offline Address Book:OfflineAddressBookIdParameter) [Move-OfflineAddressBook], LocalizedException
+ FullyQualifiedErrorId : 9250969C,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveOfflineAddressBook
However when I looked at the address books in EAC I could see that “Default Offline Address Book (Ex2012)” was the default and that it contained a copy of the Global Address List. So I did nothing else about it.
I am now at Part 3, section 7 “Move Mailboxes” and it keeps failing.
I am using the EAC so that I at least see the error as using the powershell brings back no results.
Anyway it Syncs the 18 items in the mailbox then fails with:
Data migrated: 936.7 KB (959,145 bytes)
Migration rate: 0 B (0 bytes)
Error: MigrationPermanentException: Error: An error occurred while updating a user object after the move operation. --> Unable to generate the e-mail address. Unable to load address module 'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\address\SMTP\AMD64\inproxy.dll'
for address type 'SMTP'. Additional message: 'Access is denied'.
Help??
TonyHi,
You can't configure Exchange 2013 to generate other OAB versions, and the OAB generation occurs on the Mailbox server on which the organization mailbox resides.Therefore, to move OAB generation in Exchange 2013, you must move the organization mailbox. You
can only move the OAB generation to another Exchange 2013 mailbox database. You can’t move OAB generation to a previous version of Exchange.
And please refer to the following articles :
Moving OABs between Exchange versions
If you want to upgrade from exchange 2007 to exchange 2013,I recommend you refer to the following article:
Upgrade from Exchange 2007 to Exchange 2013
Exchange version
Exchange organization coexistence
Exchange 2007
Supported with the following versions of Exchange:
Update Rollup 10 for Exchange 2007 Service Pack 3 (SP3) on all Exchange 2007 servers in the
organization, including Edge Transport servers.
Exchange 2013 Cumulative Update 2 (CU2) or later on all Exchange 2013 servers in the
organization.
Install Exchange 2013 in an Existing Exchange 2007 Organization
You can install a Microsoft Exchange Server 2013 server into an existing Exchange Server 2007 organization, and then move the Exchange resources, such as mailboxes, public folders, and connectors, to Exchange 2013. However, you can't perform an in-place
upgrade from Exchange 2007 to Exchange 2013.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support -
Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue
Hi,
I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
Configuration server Exchange 2007 SP3 :
Domain : test.com
OS : Windows 2008 server SP2 (not R2)
Firewall : OFF
Exchange roles are on separate three servers : CAS - MAILBOX - HUB.
Configuration Server Exchange 2013 :
Domain : new.com
OS: Windows 2012 R2
Firewall : OFF
This environment is on a closed network unable to reach internet.
I have try to restart the Replication service, but it didn't worked.
I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
Anyone ever had this issue?
Thanks you and have a nice day.Hi ,
Based on my knowledge below things need to checked.
1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
DataMoveReplicationConstraint : None
Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
3.Restart the Microsoft exchange mailbox replication service and check the results.
4. Have you tried moving the same mailboxes to the different databases.
5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham -
Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
"Could not find a valid mailbox migration for this organization"
Do you know that you can be?
regards
Microsoft Certified IT Professional Server AdministratorHi,
From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
Hope this can be helpful to you.
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]
Amy Wang
TechNet Community Support -
Upgrading from Exchange 2007 to Exchange 2013
Hi There,
I have two exchange serveres 2007 SP3 and they are ruining on Server 2008 Ent and 2008 R2 Ent.
I setup a server 2012 R2 and installed an exchange 2013 on it and a friend of mine helped me on setting up the new exchange server and migrating the mailboxes.
Now all the mail boxes are transferred to the 2013, and based on his recommendation I am in the stage of uninstalling exchange 2007 from my old servers.
I am reading about the process but based on the link below I have to do more things before uninstalling
http://www.exchangedictionary.com/articles/clean-uninstallation-of-exchange-2010-mailbox-server-guide
the instruction is for exchange 2010 and some shell commands are not working on shell 2007
I also found the link below:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
and I think I am at the stage 8 or 9, but I am not sure and also I do not know what to do if I am at the stage 8
Would you please advise me what shall I do to finish up the project or give me a link for it.
I have searched a lot but I was not able to find a straight forward instruction.
Thank you in AdvanceHi MAS,
Thank you for your reply
I found the instruction below:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
but I am not sure if I am in the step of moving public folders or not. I have finished the migration of all mailboxes.
When I click on "Servers" I can see the results below: -
Migrating from Exchange 2007 to exchange 2013 ( special case )
Hello ,
what is the BEST scenario ( fastest , most efficient , most secure in terms of data loss ) , to migrate from exchange 2007 ( one server , all exchange roles installed on this server , 1200 mailbox ) , to exchange 2013 ?
knowing my environment needs to be connected to their mailboxes , 24/7 !
it's very frustrating .
and i have no clue even if this is the right place to post about this , if not please refer me as to where to post .
Also , All my domain controllers are 2008 .It's fine to post your question here, and you are fine with Server 2008 Domain Controllers - that is a supported scenario.
If you haven't performed such an upgrade and you need to have 24/7 mailbox availability, I would seriously recommend you to duplicate the production environment on a test network and run through the upgrade at least once.
Most people neglect the Outlook clients requirements - they need to be updated and include several specific updates, which allow the automatic reconfiguration of internal clients. If you are preparing for this upgrade, you should be aware that all internal
Outlook clients switch to Outlook Anywhere. Clients that miss these updates will get connectivity problems.
Another common problem is the configuration of the Exchange URL - I mean the Exchange 2013 URL and the modified Exchange 2007 URL that will allow the co-existence. In your case, you definitely need to plan for co-existence - that includes requesting and
installing a new Exchange UCC (Multiple Domain Certificate) on both Exchange servers, configuring Split DNS (or preferably PinPoint DNS zones), and correct timing when replacing the existing Certificate on the Exchange 2007 server. Failure to configure the
correct URL (and it's quite easy to miss one, so triple check them) will get you in trouble.
Once you get through the switchover (switching the mail flow and Client Access through the Exchange 2013 server), move just a couple of test mailboxes and check the result.
Finally, if you are moving the Public Folders, make sure that the lock is really applied before you complete the process. Most people proceed right away and that get's the process stuck. If you can afford it (the mailboxes are already on the Exchange 2013
server at that point), just restart the Exchange 2007 server (after locking the Public Folders) and then complete the Public Folder migration.
Good Luck with the project!
Step by Step Screencasts and Video Tutorials -
New User cannot access OWA after migrate from Exchange 2007 to Exchange 2013
Dear all,
I recently migrate the Exchange server from Exchange 2007 on Windows Server 2003 to Exchange 2013 on Windows 2012 R2. I can open the mailbox moved from Exchange 2007 without any problem. However when I created a new user in Exchange 2013, the user cannot
login the OWA, the browser will throw out following screen. Can anyone help me in this case. Thanks a lot!Hi Winnie,
Thank for your reply. Below is the result, please note there has four exchange servers, HKAD and HKEX are the existing Exchange 2007 server. HKCAS1 and HKCAS2 are the new Exchange Server 2013 - both of xchange server 2013 are using owa.ksi.com.hk
as the external URL.
Identity : HKAD\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url : {}
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
https://hkad.ksi.com.hk/owa
ExternalUrl :
Identity : HKAD\Exchange (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKAD\Public (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKAD\Exchweb (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKAD\Exadmin (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKEX\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url : {}
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
https://hkex.ksi.com.hk/owa
ExternalUrl :
Identity : HKEX\Exchange (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKEX\Exadmin (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKEX\Public (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKEX\Exchweb (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url :
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
ExternalUrl :
Identity : HKCAS2\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url : {}
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
https://hkcas2.ksi.com.hk/owa
ExternalUrl :
https://owa.ksi.com.hk/owa
Identity : HKCAS1\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
ExternalAuthenticationMethods : {Fba}
Url : {}
SetPhotoURL :
Exchange2003Url :
FailbackUrl :
InternalUrl :
https://hkcas1.ksi.com.hk/owa
ExternalUrl :
https://owa.ksi.com.hk/owa -
Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.
Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11 -
Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server" -
Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.
Exchange 2013 CU5 , Exchange Power Shell very very very slow reasponse when using get command.
First my organize has Exchange on 2 site like
site A (internet facing) : 2CAS 2 MB all are Services pack1
site B (DR Site , no user active on this site) : 2CAS 2MB all are Services pack 1
so today I upgrade Exchange 2013 from SP1 to CU5 start on "site B" and I found this issue and the details is....
When I open EMS on any CU5 for query something (like get-mailboxdatabasecopystatus) the response return very slow and some query will not return at all (like get-owavirtualdirectory).
But If I using EMS on SP1. Everything is ok then I try to use EMS on SP1 connect to CU5 and try to query something. the result is
some query command cannot return for any result that are server on siteB (just some query command)
Problem
EMS on CU5 return very slow result.
EMS on SP1 still ok.
Does anyone face this problem before for CU5??? Please help me figure this out. Thank you
reply from Social.technetHi,
Have you used the above cmdlets to check your Exchange server health?
"all other command that I ran on EMS didn't logged on event viewer.", my environment is the same with you. I use Exchange 2013, only errors will be displayed in MSExchange Management. Actually, it is not related to slow EMS response.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support -
Can't get OWA to work on Essentials 2012 R2 with Exchange 2013 on second server 2012 R2 std.
I have previously with success setup a working solution with server 2012 essentials, and a second server 2012 std. with exchange 2013, I did it following this guide: http://technet.microsoft.com/en-us/library/jj200172.aspx
Unfortunately I lost the server due to a cooling error which led to an un-repairable essentials 2012, since this was a new setup and also a test setup I didn't have any working backup solution setup at the time...tsk.tsk.
Since I had to make a complete do over I chose to try out the new R2 server editions, and set it up following the same guide, when it came to this part:
Download KB2732764 for ARR 2.5, and then install the update on the server that is running Windows Server 2012 Essentials.
Copy the SSL certificate file for Exchange Server to the server that is running Windows Server 2012 Essentials. The certificate file must contain the private key, and it must be in the PFX file format.
Note
If you are using a self-issued certificate, follow the instruction in the Exchange Server article Export an Exchange Certificate to export the certificate.
Open a command window as an administrator, and then open the %ProgramFiles%\Windows Server\Bin directory.
Based on you installation scenario, follow one of these steps to configure ARR:
If you are performing a clean setup, run the following command:
ARRConfig config –cert “path to the certificate file” –hostnames “host names for Exchange Server”
I noticed that the version of "Application request routing" had changed to version 3, so obviously I didn't need to dl the 2.5 update.. When I came to the part where I wa instructed to run arrconfig config etc. I noticed
that the ARRconfig file no longer where placed where the setup guide indicated, I then went ahead and tried som manual configuration regarding certificates and such. In the end I have a working solution where Exchange and OWA is working locally but OWA isn't
working outside my local domain, the link get's placed in the RWA and is indicating the correct link for the exchange server www.remote.clinten.dk I have a certificate which include to separate domain names aforementioned and remote.clinten.dk and
I get no errors indicating certificate errors, when I try to connect to www.remote.clinten.dk/owa from outside I get a 404 error, and when I connect to www.remote.clinten.dk I get the RWA login screen for the essentials RWA. Obviously I need to set up something
in ISS probably in the url rewrite section, but I can't seem to find the right setting.. Can someone help with this?
Btw. I have found the missing arrconfig file in c:\windows\system32\essentials" and tried to run the command as described in the guide "ARRConfig config –cert “path to the certificate file” –hostnames “host
names for Exchange Server”" but it doesn't seem to work, it just prompts with a guide for using the arrconfig command and examples of correct use, I also tried removing the "" from the guide, like this "ARRConfig
config –cert path to the certificate file –hostnames host names for Exchange Server",
when I ran it without the "" It didn't prompt me with anything nor did It indicate any errors, it did not however make my OWA work either..
I am aware that exchange 2013 atm. isn't officially supported on the R2 server, but the exchange works fine inside my domain, and the pop3/smtp also works from outside, since this Is a test environment, using only my own private domain and not a company
domain I figured it would be ok to run the risk.. ;)Hi
found this on
https://social.technet.microsoft.com/Forums/en-US/1f099068-b3ed-44f3-a8c4-c22d760a8621/arr-broken-or-bad-syntax-exchange-2013-essentials-2012-r2?forum=winserveressentials
"Ok just an update for anyone else how has this issue.
The problem has been solved by Microsoft and I have included their findings below, but basically it comes down to a typo!
I often use notepad to have all the commands I need on hand, and I must have copied the command direct from the TechNet article or other website and customised the required fields. The issue with this is one of the characters did not “convert” - for want
of a better word. I should have retyped the whole command from scratch and it would have been right!
Thanks for everyone’s input and for Microsoft for getting to the bottom of it.
From Microsoft:
We have tested on your environment and here is the investigation result from our senior engineer:
================================================================
Basically the command fails due to invalid parameter, the invalid one is the ‘-‘. I think the one customer used is copied from the online document sample which translate to the unicode is 0x8211 means “en dash”, it
can’t be input by normal keyboard, so I pretty sure it is from web (mostly HTML document).
The one we check (compare) is ‘-‘ which has the code 0x45.
So it always failed to compare the parameter and ARRconfig.exe thought it is invalid parameter.
The solution is quite simple, just using keyboard to retype the command, using normal ‘-‘ and I have tried the password prompt shows
Best Regards,
Johnny Chen
Microsoft Partner Support Community Technical Support Engineer
Microsoft Global Partner Services"
Maybe you are looking for
-
Unable to see the registration assessment for an applicant created.
We have a custom requirement to create an applicant through an interface program. So, We have developed a custom program to create applicant. The applicant is getting created. Along with the applicant there is a requirement to create vacancy assessme
-
Creating a folder, within a folder
I've dumped my PC for a Mac, so still a noob! How can I create a folder, from within a folder using Finder? Every time I do, it creates the folder at the root, and I then have to move the folder to the desired location? I'm obviously missing somethin
-
Callable Statement + SQL Server 2000
I am using the Microsoft SQl Server 2000 JDBC driver and a CallableStatement (Java). The call is to a (SELECT action) stored procedure which works fine in Query Manager with the same login params. I am getting a "Could not find stored procedure" erro
-
Hi All As the title asks; 1. Are there any known issues when Editing Red Dragon raw 6k footage in Premiere Pro CC/CC14 ? 2. Which version of the software would be the best choice ? CC/CC 2014 (I have both) This is my first Red Dragon 6k Project in pr
-
Hi there I am having an issue with Logic Pro 7.1.1 and syncing of a Yamaha DM 2000. Every time I fire up Logic, I get the following message: setup>MIDI/HOST> and set •Remote 1 to "Pro Tools" •DAW ports to USB ports 2-4 I have already done this on the