Solved

i have problem with my exhcange 2013 when i open the queu i get WinRM service error and the email in outlook web app stayes in the draft and outlook anywhere in the exchange queu

Posted on 2014-12-29
20
77 Views
Last Modified: 2015-01-15
i have problem with my exhcange 2013 when i open the queu i get WinRM service error and the email in outlook web app stayes in the draft and outlook anywhere in the exchange queu
0
Comment
Question by:mohammed-khalaf
  • 14
  • 6
20 Comments
 
LVL 13

Accepted Solution

by:
Andy M earned 500 total points
ID: 40521535
I would start by checking IIS - are all of it's services started correctly? You could also do a restart (command prompt - "iisreset").

Also check event viewer on the server - any issues in Application relating to this?
0
 

Author Comment

by:mohammed-khalaf
ID: 40521884
New-Bitmap-Image.bmp
0
 

Author Comment

by:mohammed-khalaf
ID: 40521885
i have this error in the queu
0
 
LVL 13

Expert Comment

by:Andy M
ID: 40521888
Try restarting the exchange mailbox submission service. If that doesn't do anything you could try running a test-servicehealth from the EMS which may indicate any potential problems.
0
 

Author Comment

by:mohammed-khalaf
ID: 40523232
this is test-servicehealth preformed on exchange
0
 

Author Comment

by:mohammed-khalaf
ID: 40523235
and one more thing ,,, we have change the public IP address and the internal IP address from class C to A i dont know if this caused  the problem
0
 

Author Comment

by:mohammed-khalaf
ID: 40523263
event-log-error.png
0
 

Author Comment

by:mohammed-khalaf
ID: 40523268
Event-log-2.png
0
 

Author Comment

by:mohammed-khalaf
ID: 40523309
my ram consumption is 90% dose this stops exchange submission process??
0
 
LVL 13

Expert Comment

by:Andy M
ID: 40523443
High RAM consumption is a common occurrence on Exchange and 90% is typical - Exchange uses as much RAM as possible and releases it as and when applications require it (or that's the theory anyway).

I suspect changing the IP/Subnet may have caused the issues you are experiencing (especially if this was done after exchange was installed) as many of the settings in Exchange are setup on the original IP/network structure. If you can't change the network back then it may be possible to manually go through every setting in Exchange (pay close attention to DC settings, DNS, connectors, etc) and change them accordingly but it may be easier to backup the database and do a reinstall.
0
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 

Author Comment

by:mohammed-khalaf
ID: 40523491
( 441 4.4.1 Error encountered with primary target IP ) i got this error in the Queu
0
 
LVL 13

Expert Comment

by:Andy M
ID: 40523498
Sounds like it may be dns related - I would check the server dns settings and run tests to ensure that is working correctly.
0
 

Author Comment

by:mohammed-khalaf
ID: 40523508
New-Bitmap-Image--2-.bmp
0
 

Author Comment

by:mohammed-khalaf
ID: 40523509
my dns is resolving ip Names properly simple and recursive query is working
0
 
LVL 13

Expert Comment

by:Andy M
ID: 40523512
Going on the error one possibility could be faulty send connector. Try removing and re-creating the send connector then see if the problem persists.
0
 

Author Comment

by:mohammed-khalaf
ID: 40523934
i did already
0
 

Author Comment

by:mohammed-khalaf
ID: 40525076
is there a proper steps to change the Internal ip address for exchange 2013 ???
0
 

Author Comment

by:mohammed-khalaf
ID: 40525097
i returned the old ip adress and it worked properly and immediately
0
 
LVL 13

Expert Comment

by:Andy M
ID: 40525165
That  has certainly shown the IP address change caused the problem.

I'm not sure on steps myself as never had to change the IP address of a working exchange server.

The main areas I'm aware of to look for that will/may reference IP addresses are:

DNS settings (both on exchange and the network's dns records themselves, Receive Connectors, Send Connectors, Domain Controller details. Ensure that any firewall rules for exchange are changed as well (both incoming and outgoing).
0
 

Author Closing Comment

by:mohammed-khalaf
ID: 40552548
thanks
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

The Microsoft Exchange server database may become damaged or corrupted due to many reasons, such as system failure. When this happens, it is usually urgent to restore the system to a stable and working state. There are different symptoms and causes …
Resolve DNS query failed errors for Exchange
Familiarize people with the process of utilizing SQL Server functions from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Ac…
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now