• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1497
  • Last Modified:

Unable to view queue

Hi,

I am getting an error when I try to view a queue on a server.  I am able to view view the queue from the server itself but when I try to view from another server I get the following error:
---------------------------
Microsoft Exchange
---------------------------
Exchange can't connect to the RPC server on computer "EXCH-E2". Verify that you used a valid computer name. It was running the command 'get-queue -ResultSize '1000' -ReturnPageInfo $true -SortOrder '+NextHopDomain' -server 'EXCH-E2.' -SearchForward $true -BookmarkObject 'Microsoft.Exchange.Data.QueueViewer.PropertyBagBasedQueueInfo' -BookmarkIndex '-1' -IncludeBookmark $true'.

The stuff was working until I re-installed Exchange on this server.  I can resolve the name from command prompt and ping the server without any issue.
0
FundFire
Asked:
FundFire
  • 6
  • 3
1 Solution
 
imkotteesCommented:
does all the exchange services running on EXCH-E2?

you can use this command to check via powershell

Test-ServiceHealth (from local server)

Test-ServiceHealth -server servername (from remote computer)
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Please run EXBPA
Also ensure that Get-Queue is running fine with ExchangeShell

- Rancy
0
 
FundFireAuthor Commented:
All services are running on local machine.  Checked that RPC which is running on the servers.

From powershell on local everything checked OK.
from remote server I get an error that says the the remote serverr RPC server is unavailable.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
FundFireAuthor Commented:
Unable to get queue for remote server, it says that make sure service is running.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Is the remote Registry service running ?
Test-ServiceHealth

- Rancy
0
 
FundFireAuthor Commented:
Yes.  But I am thinking this might be networking issue because when I try:

telnet (ip address) 135

it fails
0
 
FundFireAuthor Commented:
It was networking.  The port was blocked.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Strange how the port just got blocked in middle of working of the server ? and if port 135 is blocked it should affect the entire server

- Rancy
0
 
FundFireAuthor Commented:
Hi Racny,

This was a brand new install.  The servers resides in Amazon EC2.
0
 
FundFireAuthor Commented:
This was a networking issue.
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now