Deprecated: Function set_magic_quotes_runtime() is deprecated in /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php on line 1505 Call Stack: 0.0001 326800 1. {main}() /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:0 0.0003 327652 2. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/index.php:25 0.0004 328940 3. require_once('/usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php') /usr/local/apache/sites/mcse.ms/htdocs/362/archive/global.php:20 0.0012 403244 4. vB_Registry->vB_Registry() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/init.php:43 0.0012 403900 5. vB_Input_Cleaner->vB_Input_Cleaner() /usr/local/apache/sites/mcse.ms/htdocs/362/includes/class_core.php:2337
Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /archive/global.php on line 26

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3113

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Chicago' for 'CDT/-5.0/DST' instead in /includes/functions.php on line 3265
windows management instrumentation doesn't work? [Archive] - MCSE
PDA

View Full Version : windows management instrumentation doesn't work?

mmac
04-04-04, 05:36 PM
something
none of the management tools work in my exchange server. tracking,
monitoring, etc. all give messages like the following:
windows management instrumentation
ID# 8004100e
exchange service manager
or
windows management instrumentation
ID#80041001
exchange service manager

When I click the Directory Access tab on the server properties I get the
following message:

Information about Directory Services could not be entirely obtained.
Check to see that microsoft exchange management service is running on
the exchange server

I have sent several posts and no one responds. I don't know why that is,
but I am posting again to several group in an attempt to get a response.
Please help if you can.
Rich Matheisen [MVP]
04-04-04, 05:36 PM
something
"mmac" <no@thank.you> wrote:

>none of the management tools work in my exchange server. tracking,
>monitoring, etc. all give messages like the following:
> windows management instrumentation
> ID# 8004100e
> exchange service manager
>or
> windows management instrumentation
> ID#80041001
> exchange service manager
>
>When I click the Directory Access tab on the server properties I get the
>following message:
>
> Information about Directory Services could not be entirely obtained.
> Check to see that microsoft exchange management service is running on
>the exchange server

well, is it?

what about the wmi service and remote registry services?

>I have sent several posts and no one responds. I don't know why that is,

because it's a newsgroup and not paid support. if nobody knows the
answer what would you have them say? if you expect immediate help,
call pss and cough up the dough.


--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
mmac
04-04-04, 05:36 PM
something
now don't get rude... I wasn't trying to be
I have a MSDN subscription and it says that I should recieve some sort of
reply from this NG within 48 hours and I hadn't. That was the reason for
comment. The people here are VERY helpful and would never suggest otherwise.
I was just surprised that I got NO reply at all.

yes, all three services are running.



"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message
news:93m070dqocun79e00rl6ikvoa3e4uqeaqg@4ax.com...
> "mmac" <no@thank.you> wrote:
>
>
> well, is it?
>
> what about the wmi service and remote registry services?
>
>
> because it's a newsgroup and not paid support. if nobody knows the
> answer what would you have them say? if you expect immediate help,
> call pss and cough up the dough.
>
>
> --
> Rich Matheisen
> MCSE+I, Exchange MVP
> MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Rich Matheisen [MVP]
04-04-04, 05:36 PM
something
"mmac" <no@thank.you> wrote:

>now don't get rude... I wasn't trying to be

twasn't rude, just truthful.

>I have a MSDN subscription and it says that I should recieve some sort of
>reply from this NG within 48 hours and I hadn't.

heh. i guess you should take that up with the msdn folks.

>That was the reason for
>comment. The people here are VERY helpful and would never suggest otherwise.
>I was just surprised that I got NO reply at all.
>
>yes, all three services are running.

and there's no event log entry from winmgt when the server's rebooted?
sounds like wmi can't connect to the right namespace. that's a problem
for the o/s folks, not exchange. exchange is a consumer of the
services, not the provider.

if there's no error when you reboot, try checking the
system32\wbem\logs directory. there may be something in there.

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
mmac
04-04-04, 05:36 PM
something
Thanks, I'm on it.
you are correct that there are no event log entries for this.
I would not have guessed that the wmi was not part of exchange, but of
course that makes sense now that you put it that way..
I looked in the log files and they will have to be interpreted by someone
other than me but I saw no glaring errors.
I'll try the 2k group next. Thanks again.

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message
news:6vm070drpkiqvt7pdpv5a766nj1np1dmnn@4ax.com...
> "mmac" <no@thank.you> wrote:
>
>
> twasn't rude, just truthful.
>
>
> heh. i guess you should take that up with the msdn folks.
>
otherwise.[color=blue]
>
> and there's no event log entry from winmgt when the server's rebooted?
> sounds like wmi can't connect to the right namespace. that's a problem
> for the o/s folks, not exchange. exchange is a consumer of the
> services, not the provider.
>
> if there's no error when you reboot, try checking the
> system32\wbem\logs directory. there may be something in there.
>
> --
> Rich Matheisen
> MCSE+I, Exchange MVP
> MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
mmac
05-13-04, 03:13 AM
something
been a while but in case anyone was wondering, the solution was found. I don't
understand it but PSS found that there were exchange files that were not entered
into the "repository"so the exchange installation had no namespace entry. Once
the files were entered into the repository everything started working
see, it WAS an exchange problem ;-)

"Rich Matheisen [MVP]" <richnews@rmcons.com.NOSPAM.COM> wrote in message
news:6vm070drpkiqvt7pdpv5a766nj1np1dmnn@4ax.com...
> "mmac" <no@thank.you> wrote:
>
>
> twasn't rude, just truthful.
>
>
> heh. i guess you should take that up with the msdn folks.
>
>
> and there's no event log entry from winmgt when the server's rebooted?
> sounds like wmi can't connect to the right namespace. that's a problem
> for the o/s folks, not exchange. exchange is a consumer of the
> services, not the provider.
>
> if there's no error when you reboot, try checking the
> system32\wbem\logs directory. there may be something in there.
>
> --
> Rich Matheisen
> MCSE+I, Exchange MVP
> MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
vBulletin v3.6.2, Copyright ©2000-2010, Jelsoft Enterprises Ltd.