Emergency IPS Service Pack to be Posted Later Today

There was an emergency notification last night that I want to be sure everyone has seen:
1. Emergency IPS Version 5.0(5) Service Pack to be Released on 10/28 to Address
CSCsa85330
An emergency service pack will be released later today (October 28, 2005) to address a high severity bug relating to Daylight Savings (bug details below). All version 5.X sensors are impacted. To resolve this bug, this service pack must be installed prior to Daylight Savings which will occur on Sunday, October 30th 2005.
Bug Details:
Bug ID: CSCsa85330
Bug Title: MainApp - core during day when switchover to daylight savings happens.
Description: Within 24 hours after a transition to or from summertime (i.e. Daylight Savings Time), the sensor may become unresponsive and not allow CLI logins if Daylight Savings Time is enabled. The MainApp process will no longer run and a core file will be generated in /usr/cids/idsRoot/log/mainApp/.
The files for the 5.0(5) service pack will be posted later today (target time is 2:00 p.m. U.S. Central). Once available they can be downloaded from the following URLs:
Sensor: http://www.cisco.com/cgi-bin/tablebuild.pl/ips5
IPS MC: http://www.cisco.com/cgi-bin/tablebuild.pl/ipsmc5sp
This Service Pack will also resolve the following known issues:
CSCsb87741 TCP streams with certain ordering may not be properly inspected
CSCsb92206 Sensor boots up in crit level 2
CSCsb87674 4215 IPS 5.0 inline mode stops transmitting packets
CSCsb84996 sensorApp fails to shutdown when sent a SIGINT from mainApp
CSCsc02898 ips sensor 5.0(4) sensorapp aborting.
CSCsc04126 sensorApp aborts for BiDirData ListObj
CSCsc15875 IPS 5.0 is unable to shun E1 channelised inft. ( Serial x/y:z)
Another bulletin will be sent out within 2 hours of the posting of this Service Pack announcing its availability.

A little more information:
If your sensor is not configured for summer-time, then your sensors will not hit CSCsa85330.
If your sensor is running version 4.x, then your sensor will not hit CSCsa85330.
But if you sensor is version 5.x, and configured for summer-time with the default settings which are used in most locations in the United States and possibly other countries. Then your sensor is likely to hit CSCsa85330.
If you are unable to install the 5.0(5) Service Pack you may want to consider disabling summer-time on your sensors before this coming Sunday when the switch over happens.
What happens if your sensor does not get upgraded before Sunday and you are using the summer-time option for handling DayLight Savings Time:
The mainApp process will core sometime during the 24 hours after the switchover happens.
With the mainApp core you will no longer be able to ssh or telnet to the sensor as the cisco userid, or any other userid with administrator, operator, or viewer privelage levels. Any monitoring tool pulling events from the sensor will loose connection to the sensor because the connection is through the web server that is part of mainApp.
How to recover:
If you have a service account, then login using the service account. Switch to user root using the command "su -" and provide the same password for root as for your service account.
As user root you will then need to execute "reboot" to reboot the sensor.
NOTE: The service account unlike the other accounts can still login even after the mainApp crash.
If you do not have a service account then the sensor will need to be rebooted by another means. If the snesor is an appliance you will need to physically power the sensor on and off. If the sensor is an IDSM-2, NM-CIDS, ASA-SSM-10, or ASA-SSM-20, then you will need to login to the switch, router, or asa and reboot or reset the module.
I will keep you posted of any other developments, and let you know when the 5.0(5) Service Pack is available.

Similar Messages

IPS service pack 7.0(7) just released...

Availability of the 7.0(7) E4 service pack for Intrusion Prevention Systems (IPS) This release delivers new features and
critical fixes. A subset of the new features includes improved diagnostic information, and additional warnings and error
messages. Cisco suggests that you deploy this service pack at the earliest opportunity.
For further information please read the full release notes here:
http://www.cisco.com/cisco/software/release.html?mdfid=282671829&catid=268438162&softwareid=282549759&release=7.0(7)E4&rellifecycle=&relind=AVAILABLE&reltype=latest

Yes I have the same issue with 7.x.
Don't know when Cisco will fix this.
Regards
Farrukh

IPS 7.0(8)E4 service pack now available!

The 7.0(8)E4 service pack has been posted and is now available for download here:
http://www.cisco.com/cisco/software/release.html?mdfid=282671829&flowid=4417&softwareid=282549759&release=7.0(8)E4&relind=AVAILABLE&rellifecycle=&reltype=latest

The difference between 7.0(5) and 7.0(5a) is just which Signature Update is included.
7.0(5) included S558
7.0(5a) included S549
The reason for including a lower signature update in 7.0(5a) is because of an issue that happened in the S550 Signature Update.
There was a change to default signatures which could cause issues in configuration.
The Signature Update installations could handle the problem and allow users to correct the issue.
The Service Pack installation, however, is not able to detect the problem and could lead to a larger problem.
So in order to prevent a Service Pack from encountering the issue we re-issued the 7.0(5) Service Pack as a 7.0(5a) Service Pack and put in a Signature level prior to the one that could cause the situation.
Both 7.0(5) and 7.0(5a) have all of the same other files on the sensor.
And if you upgrade 7.0(5) and 7.0(5a) to S567 or higher, then both versions are fully equivalent.
The only difference between the 2 was in the Sig level, and so by applying S567 they are now at the same Sig Level.
The issue with the Signature Update will only affect a few rare customers.
There is a specific signature that if tuned could cause a configuration issue. (You can look in the Readme to see which signature it was, I can't remember right now).
If you did NOT configure this signature, then both 7.0(5) and 7.0(5a) work just fine.
If you've loaded 7.0(5) and it is working, then you don't have to worry about needing to install 7.0(5a), you won't have the issue.
If you have not installed 70(5), then go ahead and use 7.0(5a) so you won't hit the issue.

How to find out the IPS and DS Service Pack and patch levels in windows server.

Hi,
I have installed the Information Platform Services 4.0 and Data services 4.0 in windows QA system, now we need to install the same version of IPS & DS in windows PRD system for this how could we find out the exact version of IPS & DS ( Service pack and patch levels ) and where we can find the same.
Many Thanks,
Sudheer

Hi Sudheer,
On a Windows Operating Systems you can check the “Programs and Features” in control panel.You can see a list of both the Name and Version number of SAP BusinessObjects that is installed.
option 2:
Open CMC go to Settings. In the properties, you will find the Product Version.
Please check below SAP notes for more information.
http://service.sap.com/sap/support/notes/1602088
Regards,
Pavan

How do i get windows xp service pack 2 or later?

When trying to install itunes, it says i need windows xp service pack 2 or later. How do i get tis i have never had this problem before

Hey menel77,
Click Start> All Programs> Windows Update, this will take you to the Microsoft update page.
Jason

Alchemy and Windows 7 post Service Pack 1

Is anyone having a problem using Creative's Alchemy application for restoring 3d hardware acceleration for old games in windows 7 AFTER installing Service Pack 1?
I have had very good luck in the past when using Alchemy under 32 or 64 bit versions of Vista and Windows 7. I no longer can make it function now and I was curious if anybody else had similar results before/after service pack 1 for Windows 7.
Thanks.
Cheers,
jmacguire

Have you try using the beta version of the Creative ALchemy Beta .43.06

Create software update group that only contains post service pack hotfixes?

I'm creating software update groups for server and workstation OS. Is there a way to exclude pre-service pack updates from an update group (or even the search itself)? Example: all of our machines already have Windows 7 SP1 installed, therefore
I don't need to include any updates that were included in SP1. I know only required updates will be installed, but I'd rather not waste disk space downloading ones I don't need. Thx

The console shows you how many devices in your hierarchy require a given update. If you don't want to see updates that are not required by any devices, select Add Criteria > Required > Greater or Equal to 1 > Search. This assumes that the Software
Updates Evaluation cycle is run on the devices...
If you apply SP1 to all devices, the individual updates (pre-SP1), should not be required by the devices (they may even become superseded by SP1 - depends)... The count of Required in the console should be 0...
I know this is not the exact answer you're looking for, but it's easy...

Windows 2008 Server R2 - Service Pack 1 Failed to install

A few nights ago I deployed Service Pack 1 for Windows 2008 Server R2 x64. The update failed to install after 3 attempts using the Windows Update manager. After the third time I checked the system properties which states that SP1 is
installed, yet it never appeared to install successfully as my other server machine had a prompt stating the SP was installed successfully.
In update history it shows the 3 failed attempts with no successes. This morning I began running into memory errors which are impacting my 2 VM Ware sessions which in turn lock up my virtual machine so I am going to attempt to remove and reinstall
to see if this corrects my issue. By the way what triggered the install of SP1 is random reboots of my server. This is that unknown Kernal Power Error which I have yet to resolve. Some months my server randomly reboots one time and other
months 4-5x. That is neither here nor there, the point of this discussion is to resolve SP1.
I have tried to remove SP1 by means of Control Panel, Programs and Features, Installed Updates. So it shows the that the SP1 installed in multiple areas yet in the install history no signs of successful installation.
When trying to uninstall from Program and Features/Installed Updates section in control panel it cycles through like its going to uninstall, but after several minutes I receive the following error      Windows Update
An error has occurred. Not all of the updates were successfully uninstalled.
When trying to uninstall from the command prompt (as administrator) "wusa.exe /uninstall /kb:976932" I get the following popup            Windows Update Standalone Installer
Installer encountered an error: 0x80073712       The component store has been corrupted.
Now if I try and install through the network installer file name "windows6.1-KB976932-X64.exe" I get "Windows Server 2008 R2 Service Pack 1 is already installed"
I performed these steps in the order mentioned which I came across this "System Update Readiness Tool for Windows Server 2008 R2 x64 Edition (KB947821) [February 2011]" After applying this hotfix I went through the same steps as mentioned above with the
exact same results.
It is unfortuante I did not come across this hotfix before I attempted install SP1 as it appears as if this would have prepared the system for SP1 installation. Currently I am in limbo with a corrupt installation of SP1 and so far no means of uninstalling
short of a reinstallation or repair of the OS which I am not willing to do at this point in time.
If anyone has any suggestions please chime in and let me know what I can try. Thanks for all the support and hopefully this post will help others in the future.

Maybe a little bit late, but I was running almost same problem on a exchange server.
Scenario:
First attempt to Update the windows patches - excluded the patches from the last 2 months.
I was kind a new to this, and didnt noticed that Windows Service pack must have at least 8GB free disk space.(Recommended)
So the C:\ partition had less then 5 GB free disk space, and I started the updates.
All went well until Windows SP1 begun running to downloading and installing.
When the installer noticed there wasnt enough space, It stopped, it give the status Failed, en when scaling up the C:\partition with another 10GB more space, the C:\partition had 18GB free disk space.
Tried to Call up a new attemp to install the SP1... but with no succes to start the SP1 installation...
I tried to reinstall but the windows update didnt get offered again to install again or resume or anything to try again...
Maybe...it is handy for Mickysoft, to check before installing, so the install wont get corrupted, and can install when c:\ partition has enough disk space.
What was the trick:
1) Stop the windows Update Service
2) C:\Windows\SoftwareDistribution\DataStore - Delete content
3) C:\Windows\SoftwareDistribution\Download - Delete content
4) Windows update Service check if its runs again
5) Check again for windows updates - Check if Windows Server Service pack 1 is offered, and install reboot and youre good to go.
It works for me :) hopefully after 3 years you had found a solution, but since I was poping for a solution and found this article with no solution.
I tought it will be hopefull for others to respond to this article with a solution.
Kind regards,
Alexander Tjintjelaar
Micky soft noob

Salesforce and Crystal Reports XI Release 2 Full build with Service Pack 2

Hi
I need to install 'Crystal Reports XI Release 2 Full build with Service Pack 2' (CR XI R2 SP2) on a new computer but can't find the exe/zip file used previously to do that.
The reason I need that particular version is because (as I understand it) its the version needed to interface with our Salesforce application.
I have the CRXI original disks and keycode but as I understand it no manner of patching with SPs will get me to CR XI R2 SP2.
I've tried various searches and frustratingly come up with only dead links (old BO forums and SAP forums).
Is there a live link somewhere that I can use, or will a later version do the job?
For example, alternatively, will I be able to use the CR XI R2 SP4 file instead?
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/bobj_download/main.htm
Thanks for your help.

Post Author: ejthunder
CA Forum: Deployment
Hello,
Crystal Reports XI and XI R2 are not supported on 64 bit machines. I have not heard of any plans to change this. As you've discovered - the only version of Crystal Reports that is supported on a 64 bit machine is CR.NET 2005 (v10.2), the version that ships with VS2005.
Your options are to downgrade your application to use bundled CR.NET 2005 or to deploy your CR XI R2 .NET application to a 32 bit machine.
EJ

Service pack 1 for windows vista home premium

Recently my computer had a virus. I had to do a complete system restore. Now that I have done this I am trying to install the service pack 1 for this operating system and I get to the third step and the progress bar hardly moves. I have let it run for
up to 8 hours and no progression. I tried to install the service pack 2 but it says I need 1 first. Need lots of help on this issue please. Windows update not catching that I need this.

Hi,
During the Windows Vista SP1 installation, this issue occurs when a third-party application holds open a file or locks a file that the Service Pack installation program
has to use. For example, a third-party antivirus or antispyware application may cause this problem. If you are running any third-party applications such as Spyblocker, Internet or web accelerators (programs designed to boost the speed of the Internet connection),
security or anti-virus programs (McAfee, Norton, etc.), I recommend temporarily disabling or shutting them down during the troubleshooting process. Please be sure to re-enable them once the process has completed.
I recommend running Reset Windows Update Tool and System Update Readiness Tool. System resources, such as file data, registry data, and even in-memory data, can develop
inconsistencies during the lifetime of the operating system. These inconsistencies can be caused by various hardware failures or software issues. In some cases, these inconsistencies can affect the Windows servicing store, and they can cause software updates
not to work. We can run Reset Windows Update Tool and System Update Readiness Tool to resolve these inconsistencies. When Reset Windows Update Tool and System Update Readiness Tool detects incorrect manifests, files, or registry data, it might replace the
incorrect data with a corrected version. Please follow the steps below.
Step 1: Run Reset Windows Update Tool and System Update Readiness Tool
1. Please download and run Reset Windows Update Tool from the link below:
http://go.microsoft.com/?linkid=9665683
2. Please download and run System Update Readiness Tool from the link below according to the System Type:
System Update Readiness Tool for Windows Vista 32-bit
http://www.microsoft.com/downloads/details.aspx?FamilyID=2889489c-ee87-4607-8aa5-812e8078ab27&DisplayLang=en
System Update Readiness Tool for Windows Vista 64-bit
http://www.microsoft.com/downloads/details.aspx?FamilyID=14f76773-007c-493f-bece-243bc21ac73d&DisplayLang=en
3. Restart the computer and install Windows Vista SP1. Let’s reinstall
SP1 standalone installer in Clean Boot.
For your reference, I have attached these steps as below:
Step 1: Download Windows Vista Service Pack 1 Standalone Installer
====================================================
1. Download Windows Vista SP1 from the link below according to the System Type:
Windows Vista Service Pack 1 for Windows Vista 32-bit (Size: 544.3MB)
http://www.microsoft.com/downloads/details.aspx?FamilyID=f559842a-9c9b-4579-b64a-09146a0ba746&DisplayLang=en
Windows Vista Service Pack 1 for Windows Vista 64-bit (Size: 873.0MB)
http://www.microsoft.com/downloads/details.aspx?FamilyID=86d267bd-dfcd-47cf-aa76-dc0626dcdf10&DisplayLang=en
2. Please save it on the Desktop.
Step 2: Install Windows Vista SP1 in Clean Boot Mode
=========================================
Please disable all startup items and third party services when booting to avoid conflict when installing
Vista SP1.:
1. Click "Start", type: MSCONFIG in the search box and press Enter.
Note: Please click "Continue" if the "User Account Control" window pops up.
2. Click "Services", check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).
3. Click "Startup", click "Disable All", click "OK" and restart the computer.
Note: Temporarily disabling the Startup Group only prevents the startup programs from loading at startup. This shouldn't affect the system or other programs. We can manually run these programs later.
4. Please double click the downloaded Windows Vista Service Pack 1 Standalone Installer and follow the instructions to install Windows
Vista SP1.
To restore the computer to use a Normal Startup, repeat step 1 above. Then click "Normal Startup" on the General tab, click "OK", and then restart the computer.
Please take your time with the steps and let me know the results at your earliest convenience. If there are any questions or concerns, please post here for further
research.
Regards,
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. ”

Different service packs in admin server and managed server

Hi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace

Hi,
Has anybody successfully used a WebLogic 6.1 SP1 managed server that
connects to a WebLogic 6.1 SP 2 admin server?
BEA's docs claim:
"The Administration Server must be running the same version of
WebLogic Server as the Managed Servers in its domain. The
Administration Server must also have the same or later service pack
installed as the Managed Servers in its domain. For example, the
Administration Server could be running version 6.1, Service Pack 2
while the Managed Servers are running version 6.1, Service Pack 1."
This is precisely what we want to do, but it's not working. In this
case, we need to run the admin server and managed server on the same
machine, but we need the managed server to run SP 1 to work around a
bug in SP 2. So to our initial installation of WebLogic 6.1 SP 2,
where I run the admin server, I added a second installation, this time
WebLogic 6.1 SP 1, with a different BEA_HOME. When I start the
managed server from this second installation, I can see from the logs
that it is starting up correctly as 6.1 SP 1. But then it fails with
a ClassCastException when connecting to the admin server (I have
included the stack trace below). This seems typical of version
compatibility problems I've had when I've tried connecting to a server
with a client of a different version.
But in this case, you are supposed to be able to have the managed
server with a lower service pack. Does this work for anybody? Has
anybody encountered the problem I'm having? Note that the servers are
not clustered, if that makes any difference, and we have a custom
security realm in addition to the default file realm (though "system"
of course is in the default file realm).
Thanks in advance for any help,
Jim Doyle
[email protected]
####<Aug 8, 2002 10:25:38 AM EDT> <Emergency> <Server></server>
<chile.iso-ne.com> <webui
server> <main> <system> <> <000000> <Unable to initialize the server:
'Fatal ini
tialization exception
Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:456)
at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:385)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace

Making the WMB54G work with Vista (Service Pack 1) - it does work.

I posted this in response to a thread, thought it could use its own topic.
There is hope and potential success for Vista users!   I got the WMB54G 2 days ago. I spent 6 hours with it and nearly threw the product AND my computer out the window the first night. I scoured this forum for the past two days, and by putting pieces together from various threads, I'm now using the Music Bridge successfully with my 1 month old Dell XPS M1530 with Vista Home Ultimate with Service pack 1.  Once I had my gameplan, it worked perfectly the first time I tried the new approach. I will try to write a step by step process of what I did in the next few days but for now.....
1. Throw out the installation CD that comes with the music bridge (its useless for Vista).... I'm kidding, but you get the point.
2. You HAVE to dowload the Vista compatible installation utility and Firmware upgrade from the Linksys forum - I don't have the link right now, but its here in this forum.
3. Run the Vista driver setup to install the Musicbridge utility - the "Install utility" link at the bottom of the setup screen, but DO NOT try to configure the router since you'll just have to do it again later.
4. Run the firmware upgrade for the router (it behaves exactly like the setup utility, but instead of configuring the hardware for use, it upgrades the fimware)
5. Run the Vista driver setup to configure the router (only after the firmware upgrade).   I didn't have to do anything outside of the auto setup. i'm using a Linksys wireless G router as well, and it connected with 64 Bit WEP encryption no problem once i entered my encryption passphrase.
6. Open up MSCONFIG and disable the CMFLYWAVE Application on Startup
7. In your Program Files directory, find \Linksys\wmb54g\wmb54g.exe, \Linksys\wmb54g\driver\cmas2ds.exe, and \Linksys\wmb54g\driver\cmflywav.exe - For all three files, right click and go to Properties\compatability.   Check the "Run this program in compatability mode for:"   pick XP with SP 2.
THANK YOU SO MUCH TO THE PEOPLE WHO POSTED THAT LAST BIT!!!!
8. I'd suggest restarting the computer now.
9. You might get a "WMB54G.exe has stopped running error" on restart... that's ok
10. Start the following files in this order:
cmas2ds.exe
cmflywav.exe
wmb54g.exe
11. The utility should start, and then you can connect to the bridge via the system tray icon. - you might have to also set the default audio device to the Music Bridge by right clicking your system tray speaker icon
12. Uncheck the "Start the Music Bridge when I start Windows" option in the utility screen - and execute the three files in step 10 each time you restart.
I hope this works for you.
Solved!
Go to Solution.

I finally got my WMB54G to work with Vista SR1. It took me 4 hours of struggling to figure it out though.
What I did was:
1. Download the latest utility and firmware from the linksys support site.
2. To set up the device, preferably use http://192.168.1.210. There are http setup instructions on the linksys customer service site. Alternately, you can use the setup wizard on the CD but I would recommend avoiding it if you can. If you do use the setup CD and it installs the WMB54G utility, promptly uninstall the utility afterwords and restart the computer.
3. Update the firmware to v.2.18 by using http://192.168.1.210 and going to the HELP tab
4. Install the latest utility from the support site but do not run the main setup. Simply run setup.exe in the utility folder AND GIVE IT PLENTY OF TIME. Walk Away and let the installer finish and close. Then do the thing people discovered -- edit the properties of C:\Program Files\Linksys\WMB54G.exe and make sure it is set for running in XP compatability mode.
5. Restart the computer
Mine started working fine after I did all of this -- the WMB54G came up automatically and found the device. Keep in mind I do not have WEP or anything -- just unsecured wireless.
Good luck.
Mike
Message Edited by jmfife on 01-17-2009 10:51 AM
Message Edited by jmfife on 01-17-2009 10:54 AM
(Mod Note: Edited due to non-compliance of forum guidelines.)
Message Edited by giantherockstar on 01-17-2009 11:05 AM

Where to find the latest Service Packs and Patches

AccAD service packs can be downloaded from SAP Service Market Place (SMP), under 'Comprised Software Component Versions'
The process for downloading the package is described below:
1. Go to SAP Support Portal - [https://service.sap.com/swdc]
2. Under Find your Software, see the 2nd bullet titled A-Z Index, and click on the link to Support Packages and Patches
3. Click on the letter A
4. Click on ACCEL. AD FOR SAP NETWEAVER
5. Click on AAD 2.2 FOR SAP NETWEAVER
6. Click on Comprised Software Component Versions
7. Click on AAD APPL DELIVERY ENGINE 2.2
8. Click on the OS version that matches your AccAD landscape
9. Scroll down to the window and find the Downloads window.
10. Look for the latest version by scrolling down further (internal scrollbar) and pay attention to the Last Changed date column.
11. Click on the link to the TGZ package which will start the download
Zeev

Hi Stephan,
I wanted to add onto Zeev's precise answer.
First of all we appreciate your feedback, we will look into why the above mentioned links are not updated as expected.
Regretfully our SDN page is a bit outdated and we are in the midst of updating it.
Currently, AccAD 2.2 SP4 as available for download and has already been adopted by some of the main SAP customers and in addition by new customers.
The release notes indicating the differences can be found as part of the installations but I hope to provide the 2.2 SP4 notes later this week - in a formal SDN announcement.
Further more as for additional updates:
- AccAD 2.3 is currently undergoing validation phase and is expected to enter Ramp Up phase in October of 2011.
- AccAD 2.3 as with every version brings with it new capabilities and increased performance and quality as well as a more up-to-date PAM.
- We are currently in the planning phase of the next AccAD version to begin development very soon and would be very happy to hear the feedback that you or any other of our customer base may have. To do so, I encourage you to contact me directly - as i cannot post an email address here - my details can be found in my business card found in this forum.
- We will be attending and presenting at SAP TechEd Las Vegas and TechEd Sapphire Madrid - we would be happy to meet up in case you will be present.
All the Best,
Smadar
Edited by: Smadar Ludomirski on Sep 11, 2011 9:29 AM

My Satellite A205-S5800 Is InCompatible With Microsoft Vista Service Packs

I don't know where Toshiba gets off saying they're compatible with the Vista Service Packs when they are most certainly NOT. I have had the SAME exact problem with SP1 & SP2. I bought this paperweight at Best Buy (NEVER shop there), with Vista Home Basic, and ran into problems one month later, when I tried upgrading to SP1 (via Windows Update). It rebooted, and then refused to load. I had to reinstall everything. Again and again this happened. I took it to Best Buy, and they told me it was a faulty hard drive. Replaced, the problems reoccurred again. So, Best Buy claimed it was the Motherboard. A fresh one installed, SP1 finally worked from stand alone download. For 9 months, no problem. Then I stupidly decided to update to SP2 (via Windows Update). The SAME exact problem. Files were corrupted. Restore points vanished. Always with reinstalling to original format. I get SP2 standalone to work, and then Microsoft Update tells me I need to update with something or other. Rebooting ONCE AGAIN prevents me from loading up anything. Bets Buy now claims it's a software issue.
So, 3 different problems caused the exact same problem. Always with Windows Update, and almost always with Service Packs. This is compatibility? Toshiba sold me a lemon, a giant paper weight. I cannot upgrade it to Service Packs, and who knows which update next will frell me over. Especially since Microsoft forces updates on us from time to time. I have every right to update this laptop to the latest Service pack or other such necessary update to keep my system secure. What happens when my vulnerable machine is hijacked and zombieifed by nogoodnicks, and the police come knocking at my door? After all is said and done, and they chastise me about not updating my system, do I tell them, "No, it's OK. Toshiba says it's totally cool not to. They think Microsoft Service packs are evil"? Believe me, this situation can and has happened before. Machines can be compromised, and police will think it's you first.
Now, who at Toshiba do I speak to about a refund/replacement? I Lemon Law (via California) you, Toshiba. You sold me a worthless hunk of junk, and that is unacceptable. I will not use a system that can't be updated because you don't like Service Packs and Windows Update. and money was not spent to not use a laptop.

I think your tinfoil hat is on too tight. If it was a problem with that model, then nobldy would be able to update Windows, and there would be thousands of posts all over the Internet.
Problems are usually caused by software, sometimes installed by the user, and sometimes installed without the users knowledge. What's the state of your malware protection? Have you scanned for rootkits?
You also might want to run the System Update Readiness Tool to find problems.

Exchange 2010 Service Pack 3 question

Forum,
We currently have a small Exchange organization consisting of one Exchange 2010 SP1 server at the corporate office and a 2nd server (mailbox) at another location. The other location also has a CAS server. We need to apply SP3 to Exchange and
have already performed the schema update for SP3.
My question is: are we able to install SP3 on the corporate Exchange server
now and apply SP3 to the remote CAS and mailbox servers later without causing any Exchange Organization issues? Server downtime at the corporate office is easier to schedule than the remote location which needs change
control notification and planning well in advance as they operate 24/7.
I just don't want to upgrade one server then cause problems throughout the Organization as Exchange is heavily used. We need to upgrade to SP3 not only because it is the latest SP that resolves a host of issues but also to prepare for
a hybrid deployment of Office 365.
Thank you in advance,
Joe

You would want to update CAS servers first, prior to any mailbox servers.
Is the single Exchange server in the corporate office multi-role?
Do you have a DAG between the two mailbox servers going over the WAN connection?
http://supertekboy.com/2014/05/01/exchange-2010-installing-service-pack-3/
Check out my latest blog posts on www.supertekboy.com A tech blog for I.T. Superheroes.

Emergency IPS Service Pack to be Posted Later Today

Similar Messages

Maybe you are looking for