Old Family plans can no longer be used?

Today is the day I am able to upgrade my phone finally so I decided to preorder the Galaxy S III. I decided I'd rather lose my unlimited data and take the final NE2 $50 discount by waiting til today to preorder. So I'm going through the process and it tells me my plan is not compatible with my new device, and it gives me the option to either move to Share Everything (which I don't want to do because it is going to cost my family $20 more per month and we have no need for unlimited minutes or shared data as I am the only smartphone) or pick a new individual plan. I was under the impression this whole time that we would not be forced onto share everything(which is true) BUT that we would be able to KEEP our current plans (excluding unlimited data feature). But as I am going through the process, it is not giving me the option to keep our current rate plan. Is this actually the case, or am I just missing something?

mdram4x4 wrote:
because he upgrading today instead of yesterday
same answer applies
any upgrade will require a current plan
sahre plan or individual
So when I upgrade my phone in 6 days I HAVE to take the new plans even though Verizon flatly stated current customers can keep the old plan.

Similar Messages

Transfering files from old MacMook that can no longer draw power to a new MacBook Pro

I have an old MacMook that can no longer draw power. I want to transfer the files from the old, broken MacBook harddrive to a new MacBook Pro that I just bought. I was curious how to do that since the old MacBook cannot use power.

Get an exterior enclosure & put the hard drive from your old Mac into it & they attach to your new computer.

Since the iOS7.0.2 update to my iPhone 4S, I can no longer choose use of my Bluetooth device if using the power cord to listen to MUSIC or answer my phone (choice of powercord as 'dock,' speaker,

Since the iOS7.0.2 update to my iPhone 4S, I can no longer choose use of my Bluetooth device if using the power cord to listen to MUSIC or answer my phone (choice of powercord as 'dock,' speaker, & phone only). Was this former-feature now an oversight?? I'd really appreciate having my Bluetooth once again listed as a choice of audio option. Especially considering the battery life is not what it was prior to this update, and requires recharging often.

Sorry to tell you but unless you have a Retail Apple Store close by, they are the only ones I have found with all the adapters and accessories. I bought an extra lightning to usb adapter the other day to use in my truck. Good luck....

I bought freehand MX, But after re-format my pc, this freehand programme can no longer be use. pls h

i bought freehand MX, But after re-format my pc, this freehand programme can no longer be use. pls help.
[ email address removed by forum host ]

And what exactly is the problem? What system? you need to be a lot more specific.
Mylenium

Another question concerning Context Expired and Can No Longer be Used error

I know this has been covered many times before - each time with essentially the same recommendations: Make sure the time zone is set for the web applications, make sure the clocks are synchornized between the hosts, adjust the timeouts (I've done defaults,
1 minute/2 minute and 5 minute/10 minute), extend security validation time outs, turn off security validation time outs.
Note of these has worked. It seems, from other folks with the issue, that this is a problem that's been stumping Microsoft as well. So I don't feel like paying them $500 bucks for a support session for this.
Has anyone come accross a better fix than the above?
Here's the latest correlation data from the logs. It points to the login timeout as the problem, but I'm at a loss as to what to do about it.
Thanks in advance.
Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. ---> Microsoft.SharePoint.SPException: The context has expired and can no longer be used. (Exception
from HRESULT: 0x80090317) ---> System.Runtime.InteropServices.COMException: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
at Microsoft.SharePoint.Library.SPRequestInternalClass.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey,
UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties,
Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)
at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32
ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32
lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)     -
-- End of inner exception stack trace ---
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32
ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32
lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)
at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout,
Boolean bAsAnonymous)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at Microsoft.SharePoint.SPWeb.EnsureSPRequest()
at Microsoft.SharePoint.SPWeb.get_Request()
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings.GetSiteNavigationSettings(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, Boolean trimmingEnabled, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid)
at Microsoft.SharePoint.Publishing.Internal.CodeBehind.AreaNavigationSettingsPage.AddChildrenToControl(String parentId, PortalSiteMapNode node, Int32 depth, Int32 maxDepth)
at Microsoft.SharePoint.Publishing.Internal.CodeBehind.AreaNavigationSettingsPage.InitializeNavigationEditSort()
at Microsoft.SharePoint.Publishing.Internal.CodeBehind.AreaNavigationSettingsPage.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.HandleError(Exception e)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
at System.Web.UI.Page.ProcessRequest()
at System.Web.UI.Page.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Barry Cohen

Hi Barry,
Thank you for your patience. Here are my suggestions about this issue:
1. Check SPNs for the application pool account for the web application ‘http://community.enet’ and take a screenshot: setSPN -L domain\app pool account (KVAERNER-NO\sno00769)
2. Ensure SharePoint WFE and APP boxes are trusted for delegation:
Trust for delegation.
Note: To perform this procedure, you must be a member of the Domain Admins group or the Enterprise Admins group in Active Directory, or you must have been delegated
the appropriate authority. As a security best practice, consider using Run as to perform this procedure.By default, no server is trusted for delegation, meaning that a service on a server in the Active Directory, cannot act on a user’s behalf, basically this
means that a service if trusted for delegation, can impersonate a user and request a Kerberos ticket in the users name.
Validate this setting in Active Directory using the following:
- Open Active Directory Users and Computers.
-In the console tree, click Computers. (Or the appropriate OU where your SharePoint Server resides)
-Right-click the computer you want to be trusted for delegation, and click Properties
-On the Delegation tab, check if ‘Trust this computer for delegation to any service (Kerberos only)’ is selected.
-Repeat this for all the servers in the SharePoint 2013 production farm.
3. Please let me know the SharePoint 2013 version. We recommend that you can upgrade to SharePoint 2013 SP1.
Best Regards,
Dats Luo

Your Voucher has been suspended and can no longer be used !!?

Hi guys,
I have purshased 2 vouchers for 2 Java exams it's been a while, they have both expiration date at 31-AUG-2013 , lately when I tried to apply them for my exam at PearsonVue a message appears and tells me that "the voucher is SUSPENDED and can no longer be used"
I don't understand what is going on and they dont even tell why it is suspended
is there something I can do about it? thanks in advance
- Kacem

I'm pretty sure that for this situation, you'll need to contact Oracle Certification Support Oracle University - Support Form. If it is the issue that I suspect, Oracle Certification Support will need to assist. Please provide the voucher numbers when you contact Oracle, they will need to know the voucher numbers and any purchase info you have - where did you purchase, how did you pay, can you provide a receipt?
Regards,
Brandye Barrington
Certification Forum Moderator

I got a error(The Content has expired and can no longer be used)

Hi,
I built a SharePoint 2013 Farm.
Infrastructure composition is:
・WebFrontEnd Server * 2(Web#1,Web#2)
・Application Server * 1
・SQL Server * 1
・OfficeWebApps Server * 1
・etc(DPM,AD,DocAve)
Site composition is:
・Community Site(Customize Site)
・Enterprise Search Center
After that, I added a WebWebFrontEnd Server(Web#3) to the SharePoint Farm.
So, I had a trouble.
The Enterprise Search Center had not been able to displayed in Web#1 and Web#2.
But, Web#3 is displayed Enterprise Search Center.
When The Enterprise Search Center had not been able to displayed, I get a error message.(The context has expired and can no longer be used. (Exception from HRESULT: 0×80090317))
Does Anyone have the same trouble?
Thanks,
Tomohiro

HI tomohiro,the issue could be of many reasons like the Time not set correctly,App pool.Please check the below link that gives more information on the resolution.
http://expertsharepoint.blogspot.de/2014/10/the-context-has-expired-and-can-no.html
Anil Avula[Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

SharePoint Navigation Error:The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

Hi,
I take a exeption on the SharePoint 2013 left navigation.
Exeption: "The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)"
I searched this exeption keyword on the internet and I find usualy 3 results
1)check datetime servers --> I checked datetime for all SP Severs ,DB server and AD server ..there is no problem
2)Disabled the WebPageSecurity Validation on CA>General Settings-->I tired and problem not solved
3) Reset IIS --> if I restart IIS problem solved but after 2-3 hours or anytime error comes again..
ULS Log:
PortalSiteMapProvider was unable to fetch children for node
at URL: /MySite/MySubSite, message: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317), stack trace:
at Microsoft.SharePoint.SPGlobal.HandleComException(COMException comEx)
at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32
ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32
lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback)
at Microsoft.SharePoint.SPGlobal.CreateSPRequestAndSetIdentity(SPSite site, String name, Boolean bNotGlobalAdminCode, String strUrl, Boolean bNotAddToContext, Byte[] UserToken, SPAppPrincipalToken appPrincipalToken, String userName, Boolean bIgnoreTokenTimeout,
Boolean bAsAnonymous)
at Microsoft.SharePoint.SPWeb.InitializeSPRequest()
at Microsoft.SharePoint.SPWeb.EnsureSPRequest()
at Microsoft.SharePoint.SPWeb.get_Request()
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings..ctor(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.SiteNavigationSettings.GetSiteNavigationSettings(SPSite site)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, Boolean trimmingEnabled, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedTypes, NodeTypes includedHiddenTypes, OrderingMethod ordering, AutomaticSortingMethod method, Boolean ascending, Int32 lcid)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapNode.GetNavigationChildren(NodeTypes includedHiddenTypes)
at Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider.GetChildNodes(PortalSiteMapNode node, NodeTypes includedHiddenTypes)
Plaase Help.

Hi Veli,
Please check the security token timeout value and it is set to 1440 as expected by default. You can check via running the command:
stsadm -o getproperty -pn token-timeout
Then check the OOB recycle times of the probkematic web application pool, and add daily recycle times for the problematic web application pool. You can do as the article:
http://technet.microsoft.com/en-us/library/cc754494(v=WS.10).aspx
Best Regards,
Wendy
Wendy Li
TechNet Community Support

The context has expired and can no longer be used. (Exception from HRESULT: 0×80090317)

I have followed the instructions on this blog. http://blog.cloudshare.com/2012/10/22/how-to-fix-sharepoint-2013-web-application-error-the-context-has-expired-and-can-no-longer-be-used/ and
it fixes the problem for a short time. I have to keep doing IISResets to get my farm backup.
Please Help.

Have you trid Ajay Khanna's suggestion from the comments field?
From Central Admin- Select the web application and Select --> Web Application General Settings --> Navigate to 'Web page Security validation', change or disable the timeout field.
Steven Andrews
SharePoint Business Analyst: LiveNation Entertainment
Blog: baron72.wordpress.com
Twitter: Follow @backpackerd00d
My Wiki Articles:
CodePlex Corner Series
Please remember to mark your question as "answered" if this solves (or helps) your problem.

The context has expired and can no longer be used

I am running across a repeatable error when accessing a specific Site Collection. EVERY TIME the SC is loaded we receive the error 'The context has expired and can no longer be used'.
I have already validated the SharePoint servers' time zones are all the same and match the web application(s), as well as set the 'Web
page Security validation' to "Off".
What else could I be missing? Could this have anything to do with Distributed Cache?
- Rick

Hi,
We just began to have the same error. The servers are also correctly set for the timezone (UTC) as well as the Web Applications.
The error happens for every site collections, there isn't a specific site where I'm able to reproduce the issue.
This is the ULS :
05/27/2014 12:59:05.98 w3wp.exe (0x1524) 0x0780 Web Content Management Publishing Cache ahh6l Verbose CreateListItemFromUrl : Parameters url : '/sitename/SitePages/Home.aspx', enableCheckedOutItem : 'True', checkedOutByCurrentUser 'False' retVal Id = '4618889e-0e1c-4503-a7fb-70fd36e2661d'. 01ff949c-98cc-d0fb-9795-c691c2852f54
05/27/2014 12:59:05.98 w3wp.exe (0x1524) 0x0780 Web Content Management Publishing Cache ahh6l Verbose CreateListItemFromUrl : Parameters url : '/sitename/SitePages/Home.aspx', enableCheckedOutItem : 'True', checkedOutByCurrentUser 'False' retVal Id = '4618889e-0e1c-4503-a7fb-70fd36e2661d'. 01ff949c-98cc-d0fb-9795-c691c2852f54
05/27/2014 12:59:06.00 w3wp.exe (0x1524) 0x0780 SharePoint Foundation Runtime tkau Unexpected System.Runtime.InteropServices.COMException: The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317) at Microsoft.SharePoint.Library.SPRequestInternalClass.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback) at Microsoft.SharePoint.Library.SPRequest.SetHttpParameters(String bstrHttpMethod, String bstrRequestDigest, UInt32 flags, Guid gTranLockerId, Byte[]& ppsaImpersonateUserToken, Boolean bIgnoreTimeout, String bstrUserLogin, String bstrUserKey, UInt32 ulRoleCount, String bstrRoles, Boolean bWindowsMode, String bstrAppPrincipalName, Boolean bIsHostHeaderAppPrincipal, String bstrOriginalAppPrincipalIdentifier, ApplicationPrincipalInfo& pAppUserInfo, Boolean bInvalidateCachedConfigurationProperties, Int32 lAppDomainId, ISPManagedObjectFactory pFactory, Boolean bCallstack, ISPDataCallback pCanaryCallback) 01ff949c-98cc-d0fb-9795-c691c2852f54

The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)

We have a problem with our wiki site collection. Once a day (and sometimes more), we get the following error message :
The context has expired and can no longer be used. (Exception from HRESULT: 0x80090317)
This message is displayed to everyone, and will stay there for an hour or so before the collection is back to life.
Doing an iisreset would get the site working but that will last for a day at the most.
This is what we checked and tried so far :
1. Our time zones are set and are correct.
2. Changing the timeout or disabling the web page security validation (followed by an iisreset) didn't work.
3. All server use the same NTP server for time sync (and they are indeed in sync).
4. It is happening only on the wiki collection, not the other collections.
5. We are unable to reproduce the behavior on the staging servers.
Some particularities :
1. Regional settings are set to French (Canada)
2. We have 500+ wiki pages in the site collection
3. We require page check-out / check-in for editing. Tried without, same problem.
Any ideas as to what should we try next ?
Regards,
homerggg

Hi,
I don't think we have changed them from the default, a quick look shows ours are set to:
Token-timeout = 24hrs
FormsTokenLifetime = 10hrs
WindowsTokenLifetime = 10hrs
LogonTokenCacheExpirationWindow = 10m
Rob

The context has expired and can no longer be used errors making farm unusable

There are a couple of other posts on this forum about the message "The context has expired and can no longer be used" but they all suggest something related to time and time zone differences. This is not the case in my farm and I have disabled
the security checking of requests on my web applications. Hopefully someone at Microsoft is very aware of this and is working to resolve it because my farm and many others are unusable like this.
I have dug through all of the ULS errors when it happens and there is nothing useful. It barely even registers as a message although, I have not turned on verbose logging, which I am about to try. I have SP 1 installed. Just to be clear, this is happening
on SharePoint 2013 Enterprise.
I have been fighting this for a month. I can add a few things about the farm I am trying to fix:
1. It was a WSS 3.0 farm that when through a 2007-2010-2013 migration in short order.
2. I believe it is under-powered on the hardware side. All VMs on a host shared with 40 other VMs, some fairly busy. Here's the virtual farm breakdown:
-1 WFE with 12GB RAM and 2 cores
-3 app servers with similar resources
-No paging file on C: on any VM. This is a decision by sysadmin. Paging on D: is system managed. Probably irrelevant.
3. Rapidly clicking from link to link seems to bring on the failure much sooner.
Any suggestions even about how to troubleshoot this would be appreciated.

Ultimately, I think it is a time sync issue across the farm. We still have request management off on all boxes because I cannot get the admins to resolve this issue but, in my lab environment I ran into a similar thing.
I may turn RM back on later to see if it comes back but here's what I think happens: In production we have 2 ESXi hosts and our SP environment is all AD (of course). The clocks are all out of sync, sometimes beyond 5 minutes. (The time sync for AD is something
I believe a lot of admins don't understand when running virtual.)
If you allow ESXi to try to sync the time for all guests you run into problems. Maybe they are more pronounced with SharePoint. Anyway, VMware and AD start fighting over the time (check your event logs) and, for us, the clocks across the domain get out of
sync beyond the 5 minute allowable window.
I recommend disabling time sync from host to guest and do what MS recommends: make your domain controller the master time server and configure it to get its time from a reliable source (which can be a single hardware host over NTP). Make other domain controllers
sync from the PDC. The other windows machines will all sync to the domain when they log in. This will prevent SharePoint from issuing tokens from one machine that are out of sync time-wise with the other machines and thus throwing the "Context has expired
and can no longer be used" errors.
Note that disabling host to guest time sync is not as simple as just clearing / un-checking the box in the VSphere client. That doesn't do it. You will need to Google for the 6 or so custom properties you must add to each guest to prevent VMWare from re-synchronizing
after certain hardware events.

The Context has expired and can no longer be used error

Hello All,
I am getting ‘The context has expired and can no longer be used.’ error.
The last thing that was modified on the farm was Distributed Cache Service.
We stopped it on the application server and only have it run on the two WFE’s servers.
Also the cache size was changed to 2048MB.
Is it possible that this change is causing the error?
We don’t have ‘Default Time Zone’ selected for the web application.
But we never saw this error till now.
Any suggestions?
Thank you,
Zabcia

Hi Zabcia,
Thanks for posting this issue,
following could be the reason of raising this issue
1. Security context of your session might be expired
2. Somebody/you might have change the data time of your server.
you can follow below mentioned steps to fix this issue
Just change/update the Date/Time in the SharePoint server
Increase the Security context in SharePoint central admin. This can be done by following the below steps:
Go to central admin
Go to "Application management section" Go to "Web Application General Settings"
Go to "Web page Security validation" section & increase the timeout field. Or, you can simply disable this option.
I hope this is helpful to you, mark it as Helpful.
If this works, Please mark it as Answered.
Regards,
Dharmendra Singh (MCPD-EA | MCTS)
Blog : http://sharepoint-community.net/profile/DharmendraSingh

Often, Firefox app will close, but the underlying Windows process will not and cannot be stopped via Task Manager. When this happens, Firefox can no longer be used...the system must be rebooted.

Hello,
Often, the Firefox app will close, but the underlying Windows process will not and cannot be stopped via Task Manager. When this happens, Firefox can no longer be used...the system must be rebooted. This happens especially when many apps are running but even though there are plenty of memory resources available.
I have tried to find if something is using Firefox in the background, but have no way to know what that would be.
Their are no apparent viruses detected.
Firefox is version v5.0 and occurred in earlier release.
System is Windows 7 (64bit).

well, it's not the same hardware and it's a bit different.
I managed to pass that stage somehow but I still have a problem
I don't use the built-in creator tool that comes with Spyrus as it doesn't know how to append a pre-staged media that was created by SCCM that should apply the Windows file system to a second partition and the WinPE to the first partition.
I managed to do everything. my only problem is that the WTGCreator that comes with SCCM 2012 R2 creates the 350MB partition with FAT32 file system.
when I boot from the device I get the WinPE, I can choose a task sequence and then it fails when trying to apply the wim file. the error tells me that the 350MB partition is FAT32 which is not supported (even though it chooses the second partition, which
is all the rest of the disk space)
what I did was adding another task that converts the 32 Fat partition to an NTFS partition and then the process continues and finishes successfully! but that's a workaround.
I'm trying to make this process as smooth as possible without having additional steps
Tamir Levy

WARNING: NEW-PAGE PRINT can no longer be used to print dialog box

i am getting a warning as 'NEW-PAGE PRINT can no longer be used to print dialog box'. Please suggest what method can i use otherwise

Please create a screenshot of the problem you're seeing by following the guide mentioned at [[How do I create a screenshot of my problem?]].
Once you've done this, attach the saved screenshot file to your forum post by clicking the '''Browse...''' button below the ''Post your reply'' box. This will help us to visualize the problem.
'''Try the Firefox Safe Mode''' to see how it works there. The Safe Mode is a troubleshooting mode, which disables most add-ons.''
''(If you're not using it, switch to the Default theme.)''
* You can open the Firefox 4.0+ Safe Mode by holding the '''Shift''' key when you use the Firefox desktop or Start menu shortcut.
* Or use the Help menu item and click on the '''Restart with Add-ons Disabled...''' menu item while Firefox is running.
''Don't select anything right now, just use "'Start in Safe Mode"''
''To exit the Firefox Safe Mode, just close Firefox and wait a few seconds before using the Firefox shortcut (without the Shift key) to open it again.''
'''''If it is good in the Firefox Safe Mode''''', your problem is probably caused by an extension, and you need to figure out which one.
Please follow the [[Troubleshooting extensions and themes]] article for that.
''When you figure out what's causing your issues, please let us know. It might help other users who have the same problem.''

Old Family plans can no longer be used?

Similar Messages

Maybe you are looking for