Cannot migrate exchange 2013 user to another database through EMC, only powershell works?

Hi Everyone,
I'm trying to migrate a few mailboxes from a database called "primary" to "archive". I can migrate a single user through powershell, however I cannot migrate users through the GUI. When the "syncing" starts, it reverts the total
from "2" to "0" and makes it appear as though I never added any users to the batch job. The job then completes "successfully"
I can see the users in the job before I hit start. Any idea why my job goes blank?
I'm running exchange 2013 CU6

Hi ,
Thank you for your question.
We could refer to the following steps to troubleshoot:
Restart IIS to check if the issue persist.
End up of the user job to check if the issue persist.
Create a new account to check if the issue persist.
We could check relevant application log, then we could check if EAC and EMS connect to same domain controller, then we could check sync between Exchange server and domain controller.
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

Similar Messages

Exchange 2013 users cannot open public folders on exchange 2010

Migrating from Exchange 2010 SP3 to Exchange 2013 CU3 in same forest and domain
client version is outlook 2013
outlook any where is disable (default) on exchange 2010 which must be disabled as organization policy
outlook any where external host name field is blank (we need to keep outlook any where disable for external)
outlook anywhere internal authentication is set to NTLM and Client require SSL to false
I have moved a mailbox from Exchange 2010 to Exchange 2013, user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010. I have been stuck on this kindly suggest

Hello,
Please explain the sentence "The user moved from exchange 2010 to 2013 cannot access public folder on exchange 2010". Do you mean the moved user can't see the public folder or the user has no permission to see the public folder?
If the moved user can't see the public folder, please check if the moved user can see the public folder via owa. When you use outlook to view public folder, you can following the method: Open outlook, click folder list at the bottom of left panel.
If the user has no permission to see the public folder, please check the permission.
=============================================================
1. Open ADSIEDIT.
2. Navigation to CN=Configuration, DC=Your domain name -> CN=Services ->CN=Microsoft Exchange ->CN=Your organization name ->CN=Administrative Groups ->CN=Exchange
Administrative Group ->CN=Databases ->CN= PF Database.
3. Right-click the PF Database, and then select Properties. Under Security, check if everyone has read permission.
Besides, please check if public folder replication is ok. You can use Get-PublicFolderStatistics cmdlet to compare item count, size.
Additional article for your reference.
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Calander Sharing Permission is not effective between Exchange 2007 & Exchange 2013 User

When a Exchange 2013 mailbox user share a calander with user in Exchange 2007 with OWNER permission, but Exchange 2007 user cannot modify or view full details of Exchange 2013 user calander.
And same behavior from Exch2007 user sharing calander with Exch2013 user.
In both scnarioes we can view only free/busy information. Cannot see full details of the meetings, cannot edit/modify. But permissions are set correctly.
Getting Yes or No prompt window with message "You dont have permission to view the calander, Do you want to as User A to share his or her calander with you?"
We are in Co exsistance with Exch2007 and Exch2013 CU3.

Hi,
Does the issue happen to all users? What about Exchange 2007 users share calendar with Exch2007 users?
Please double check whether calendar permissions are configured properly. If possible, we can remove the permission in Outlook then re-add it back later to check whether it works.
Thanks,
Winnie Liang
TechNet Community Support

How can I migrate from one user to another within the same computer?

My main user account in my desktop is becoming buggy after to many migrations from different computers and long time usage. I would like to migrate from one user to another user within the same computer to see if this improves my current problems.
How can I do it in a reasonably safe and quick way?
Thank you very much, cheers, Rui
iMAC, OS 10.6.8... and yes, I love Snow Leopard light and handy... and all my programs work on it...

Move small groups of files to the /Users/Shared/ folder or another location and see if the problems disappear. Moving everything to a new user account will in all probability transfer the problems.
(119885)

Exchange 2013 user cannot mail 2010 user

Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7
Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.
I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere
on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed
- thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?
Cheers, db.

Hi Dennis,
if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".
1. run a Powershell or CMD
2. telnet exchange2013server 25
Does it connect using the Exchange 2013 CAS / Transport Server Name?
If no, please check
1. is there any anti Virus / Firewall Software blocking the Connection?
2. is there any Firewall on the Network blocking the SMTP Connection?
3. does your receive connector include the subnet of your Exchange 2013 CAS server?
If you cannot connect verify please the remote IP range includes your new servers , check it running
Get-ReceiveConnector | fl name,binding,remoteipranges
from Powershell. If required, use set-receiveconnector to Change it.
http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx
Regards,
Martin

Exchange 2013 ECP shows no databases. User moves fail referencing an old database of a crashed 2010 server

Our old 2010 server was migrated to 2013 but before removal, the 2010 server failed. Now when I go to my ECP > Servers > Databases, the list is empty. I can't move any users either as the list population fails because it can't find the
old database from the 2010 server. I thought I removed it all from ASDIEdit but something is lingering. Mail is flowing fine at the moment.

Server has been rebooted several times with no success. These are production mailboxes.
Log Name: Application
Source: MSExchangeTransportDelivery
Date: 4/14/2014 5:53:45 AM
Event ID: 5006
Task Category: Routing
Level: Warning
Keywords: Classic
User: N/A
Computer: MAIL1.onshoreit.local
Description:
Cannot find information about owning Mailbox Server CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local
for database CN=DFMCO_PUB_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local in routing tables with timestamp 4/14/2014 10:53:45
AM. Recipients will not be routed to this database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeTransportDelivery" />
<EventID Qualifiers="32772">5006</EventID>
<Level>3</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-14T10:53:45.000000000Z" />
<EventRecordID>663745</EventRecordID>
<Channel>Application</Channel>
<Computer>MAIL1.onshoreit.local</Computer>
<Security />
</System>
<EventData>
<Data>CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>CN=DFMCO_PUB_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>4/14/2014 10:53:45 AM</Data>
</EventData>
</Event>
Log Name: Application
Source: MSExchangeTransportDelivery
Date: 4/14/2014 5:53:45 AM
Event ID: 5006
Task Category: Routing
Level: Warning
Keywords: Classic
User: N/A
Computer: MAIL1.onshoreit.local
Description:
Cannot find information about owning Mailbox Server CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local
for database CN=DFMCO_MAIL_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local in routing tables with timestamp 4/14/2014 10:53:45
AM. Recipients will not be routed to this database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeTransportDelivery" />
<EventID Qualifiers="32772">5006</EventID>
<Level>3</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-14T10:53:45.000000000Z" />
<EventRecordID>663744</EventRecordID>
<Channel>Application</Channel>
<Computer>MAIL1.onshoreit.local</Computer>
<Security />
</System>
<EventData>
<Data>CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>CN=DFMCO_MAIL_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>4/14/2014 10:53:45 AM</Data>
</EventData>
</Event>
The 2010 box is dead and unable to be restored.

Exchange 2010 users cannot open Exchange 2013 shared mailbox

Title says it all.
We're in the process of migrating 1000+ mailboxes to Exchange 2013. A number of shared mailboxes have been migrated, but those users still on 2010 cannot open them.
Is this just how it is, or is there a way around it?

Hi,
I tested in my lab, if the shared mailbox is on Exchange 2010, I could open this shared mailbox successfully. Then I moved this shared mailbox to Exchange 2013, after that, I couldn’t open it anymore, I got the following error:
Besides, I tried to open a shared mailbox on Exchange 2013 which was not moved from Exchange 2010, it is the same error message.
Based on the test, it seems that Exchange 2010 users can’t open shared mailbox on Exchange 2013. So I recommend you move those users to Exchange 2013.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 User cannot view public folders

Good morning,
User was able to view public folders, then lost connection to public folders. User cannot view public folders in OWA.
Verified proper permissions. No changes have been made to the user account in AD, exchange.

Did you do a fresh install of Exchange, meaning there was no version of Exchange installed previously? If not, have you moved Public Folders over to Exchange 2013 yet? If the answer to this question is no, then you will not be able to view Public
Folders in OWA until they are migrated over Exchange 2013.

Exchange 2013 Users cannot access Public folder in Exchange 2007 SP3

Dears,
i am working in Upgrading Exchange 2007 to Exchange 2013 CU7,, I came to know with CU7 we have new way for coexistence with legacy Public Folder
https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx
i did the steps exactly as it is in the article, but now users in Exchange 2013 always prompt for username /password when opening outlook and i found they still trying to connect to Exchange 2007 PF Server using HTTPS and failed..
BTW, Outlook anywhere is disabled in EX2007 and as per this article Q/A , it is no more needed
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
the issue now, still users getting prompted and cannot connect to PF in EX2007,,
your help is appreciated
thanks
Mufleh

I ran into the same situation recently, and found out that you need to make sure InternalClientsRequireSSL is set to false.
To verify: Run Get-OutlookAnywhere | fl Identity, *ssl
If it is true, try setting it to false.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Cannot Move Exchange 2013 Database "Object couldn't be found on" Error

Hello,
I am trying to move my exchange 2013 database to a different partition, when I enter the move-databasepath command, It says the operation couldn't be performed because object "databaseName" could not be found on "Southwestdc01"
My Exchange server name is SWPSExchange, I am in the exchange management shell on my exchange server, but it's as if it is looking for the database on my Active directory server. I have one DC, and an exchange server. Is there a way to specify
which server the database is on? If it would only look for the database on the SWPSExchange, it would work.
i verified the database name, the issue is when I run the move-database command, it is looking for the database on the wrong server.
Thanks for the help!

Here is all the info:
My Exchange 2013 server is SWPSExchange, My AD Server is Southwestdc01, I am logged into the exchange server management shell on SWPSExchange, below is what I get, as you can see it is trying to find the database on Southwestdc01 instead of SWPSExchange.
[PS] C:\Windows\system32>Get-MailboxDatabase
Name                           Server          Recovery
ReplicationType
Mailbox Database 1279379856    SWPSEXCHANGE    False           None
PS] C:\Windows\system32>Move-DatabasePath -Identity 1279379856 -EdbFilePath E:\ExchangeDatabase\1279379856.edb
The operation couldn't be performed because object '1279379856' couldn't be found on 'SOUTHWESTDC01.Southwest.local'.
    + CategoryInfo          : NotSpecified: (:) [Move-DatabasePath], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : 3961D47F,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveDatabasePath
    + PSComputerName        : swpsexchange.southwest.local

Cannot move Exchange 2013 "Discovery Search Mailbox" to DAG database! :(

I want to get rid of the default mailbox database but it won't allow me because it says it still have mailboxes. I ran:
"Get-mailbox -database "Default Mailboxdatabase name" and it shows the "DiscoverySearchMailbox" still there. I was able to move all the other arbitration mailboxes to my DAG database.
I then ran:
Get-mailbox -database "DB Name" | new-moverequest -targetdatabase "DB Name"
and
Get-Mailbox -Filter { RecipientTypeDetails -eq "DiscoveryMailbox" } | new-moverequest -targetdatabase "DB Name"
and both times I receive a long error:
MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142)
Diagnostic context:
Lid: 41192 dwParam: 0x1
Lid: 49384
Lid: 51176 StoreEc: 0x476
Lid: 48104
Lid: 39912 StoreEc: 0x476
Lid: 41192 dwParam: 0x2
Lid: 49384
Lid: 51176 StoreEc: 0x476
Lid: 48104
Lid: 39912 StoreEc: 0x476
Lid: 41192 dwParam: 0x0
Lid: 49064 dwParam: 0x1
Lid: 38439 EMSMDBPOOL.EcPoolConnect called [length=48]
Lid: 54823 EMSMDBPOOL.EcPoolConnect returned [ec=0x476][length=20][latency=0]
Lid: 53361 StoreEc: 0x476
Lid: 51859
Lid: 33649 StoreEc: 0x476
Lid: 43315
Lid: 58225 StoreEc: 0x476
Lid: 39912 StoreEc: 0x476
Lid: 54129 StoreEc: 0x476
Lid: 50519
Lid: 59735 StoreEc: 0x476
Lid: 59199
Lid: 27356 StoreEc: 0x476
Lid: 65279
Lid: 52465 StoreEc: 0x476
Lid: 60065
Lid: 33777 StoreEc: 0x476
Lid: 59805
Lid: 52487 StoreEc: 0x476
Lid: 19778
Lid: 27970 StoreEc: 0x476
Lid: 17730
Lid: 25922 StoreEc: 0x476
+ CategoryInfo : NotSpecified: (:) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : [Server=LA3-EXMBW002,RequestId=cb04b084-0dd7-46b9-bf57-6d3317013d47,TimeStamp=3/14/2014 10:44:34 PM] 7A53F855,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
Any ideas on moving that Discovery Mailbox? Thx!

MapiExceptionMdbOffline: Unable to make connection to the server. (hr=0x80004005, ec=1142)
That error indicates that the database is not mounted, so mounted and try again.
A workaround if you can't move the mailbox, is to rehome the mailbox to another database.
Example:
Get-Mailbox Discover* | Set-Mailbox -database <DB Name>
Martina Miskovic

Cannot uninstall Exchange 2013 - Cannot get ecp page too.

I am trying to install Exchange 2013 and we already have Exchange 2007 in our production environment.
Running the command get-exchangeserver |fl give the following. It shows IsCleintAccessServer : False, I am pretty sure I did select both the roles at the time of installation.
IsHubTransportServer            : True
IsClientAccessServer            : False
IsExchange2007OrLater           : True
IsEdgeServer                    : False
IsMailboxServer                 : True
IsE14OrLater                    : True
IsE15OrLater                    : True
IsProvisionedServer             : False
IsUnifiedMessagingServer        : True
IsFrontendTransportServer       : False
I can see all the virtual folders in IIS and while trying to access the ecp page using https://localhost:444/ecp?exchclientver=15, it says "Sorry! Access Denied".
Get-ecpvirtualdirectory gives no output.
If I try to uninstall I get the following error.
Error:
Uninstall can't continue. Database Mailbox Database 0424069483 : This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or arbitration mailboxes. To get a list of all mailboxes in this database, run the
command Get-Mailbox -Database <Database ID>. To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive.
To get a list of all public folder mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -PublicFolder. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration.
To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -Archive.
To disable a public folder mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>.
If this is the last server in the organization, run the command Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command
Set-MailboxPlan <MailboxPlan ID> -Database <Database ID>. It was running the command 'Remove-MailboxDatabase 'CN=Mailbox Database 0424069483,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=XYZ,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=XYZ,DC=X,DC=X' -whatif'.
I would like to uninstall this server and do a fresh install. Tried recover option too, still facing same problem.
HELP!!!

Hi,
I suggest re-install CAS role for test whether it works.
If not, please uninstall the MBX role as what you want. I suggest make a full backup if there is any data in the Exchange server, then remove the mailbox database.
Found an article for your reference:
Cannot remove mailbox database
http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.unwillingtoremovemailboxdatabase(v=exchg.150).aspx
After uninstall the Exchange server, I suggest double check whether there is anything leave in AD via ADSIEdit tool. Then re-install Exchange server.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 users cant connect to public folders on Exchange 2010

Hi
I recently migrated all users from exchange 2010 to 2013 and now nobody can connect to public folders.
Ive read several forums with similar issue, but none of the solutions have fixed my problem.
My configuration on exchange 2013:
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
ive also removed negotiation from the rpc site on the IIS.
Is there something else im missing?
Thanks
/Carlos

Are you getting any error message when accessing the Public Folder?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Outlook clients cannot connect Exchange 2013 cutover from 2010

Hello,
My company has been running an Exchange 2013/2010 coexistence. Currently, Exch 2013 (2mbx and 1 CAS) utilizes "mail2.domain.com" for the name space. Exch 2010 (1MBX 1 CAS) uses "mail.domain.com"
We recently attempted to cutover external and internal DNS to point "mail.domain.com" and "autodiscover.domain.com" to the Exch 2013 server.
We changed all virtual directories on 2013 to use "https://mail.domain.com/owa" (ECP, EWS, etc. were changed too) for the internal and external URL. The Exch 2010 virtual directories internal URL are set to "https://internalFQDN.domain.com/owa"
the external URLs are $null
Both CAS servers were setup to use Outlook Anywhere since this is how 2013 proxies to 2010. The internal URLs for both were set to "mail.domain.com" IIS authentication Methods (Basic, NTLM). ClientAuthenicsationMethod: NTLM.
For both servers the autodiscoverserviceinternaluri was set to: https://autodiscover.domain.com/autodiscover/autodiscover.xml
The 2013 server has two SSL certificates installed. One is a wildcard cert for "*.domain.com" and the other includes our SANs (mail.domain.com, mail2.domain.com, webmail.domain.com, autodiscover.domain.com) it also includes the FQDN for the 2010
and 2013 CAS servers.
I'm speaking in the past tense because we had to roll back. The problem was no Outlook user could connect. This goes for mailboxes hosted on the Exchange 2013 and 2010 servers. The error was: "Cannot
open your default e-mail folder" to "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete".
Everything else worked fine during the cutover. OWA 2013 login page proxied 2010 logins properly, Outlook 2011 could connect with EWS fine, Active-Sync worked without issues too.
It was only the Outlook 2010 and 2013 clients that could not connect.
We rolled back and everything is working as it was before with the separate namespace. That leads me to think it's something with Outlook Anywhere (RPC/HTTPS)
but the settings seem correct unless I'm missing something. Any help is appreciated.
Thanks!

Hard to say. I've had to change the router to point to the old server as mail wasnt getting in. But OWA did seem ok, although I couldn't send messages... I could only see the inbox and contacts etc.

Cannot grant access a user to a database

Hello...
I am using SQL Server 2012 Express Management Studio. I have a database with a user which is db_owner of a database.
I have created another database and I need that user to have full access to it. I have created the user and assigned to the database as a db_owner, but when I connect using that user, I can expand database node, however, I did not see any table.
As "sa" user, I edit user properties however I cannot add explicit persmissions to the database tables because in protectable elements in user properties does not show any tables.
Any help will be appreciated,
thanks
Jaime
Powered by C++

Hi Jaime,
According to your description, you are unable to see any tables using the login account which has db_owner database role in the database. I agree with Ashwin that your table is created in other database if you indeed create the table. You could verify this
using the code below to find the database in which your table resides by replacing 'your_table_name' with the table name.
sp_MSforeachdb 'SELECT "?" AS DB, * FROM [?].sys.tables WHERE name like ''%your_table_name%'''
In addition, if you create tables using Transact-SQL, please make sure to use the statement “USE { database }“ to change the database context to the specified database.
Regards,
Michelle Li

Cannot migrate exchange 2013 user to another database through EMC, only powershell works?

Similar Messages

Maybe you are looking for