Upgrading from Project Server 2010 to 2013 ConvertTo-SPProjectDatabase gives error (Convertto-SPProjectDatabase : Action 15.0.38.0 of Microsoft.Office.Project.Server.Upgrade.PublishedDatabaseSequence)

Getting the error on subject line when I try to upgrade from Project 2010 to 2013

Hi,
Do you get and error when the command is executed or when you try to start the execution (the command is not valid)?
If you get the error when you try to start the execution, I would suggest re-typing the command and make sure all parameters are valid.
Please give us the error details if you get the error when the command is running
Paul

Similar Messages

Action 15.0.0.1 of Microsoft.Office.Project.Server.Upgrade.FullFarmDependentProjectDatabaseSequence failed

Hi
I try to upgrade a Project Server 2010 environment to 2013. When I run
upgrade-spprojectwebinstance
it fails with:
Action 15.0.0.1 of Microsoft.Office.Project.Server.Upgrade.FullFarmDependentProjectDatabaseSequence failed
Anyone seen this error?
Thanks

Hi Xtenser
try to check the ULS log. There might be a hint, that there is a blocking job in the Project Server Queue. This can block the upgrade process.
Regards
Christoph
Christoph Muelder | Senior Consultant, MCTS, MCSE, MCT | SOLVIN information management GmbH, Germany

What Project Server 2010 and 2013 make possible in terms of timesheeting, "freezing" timesheets and expenses.

We have recently gone live on a Timesheeting system based on Project Server 2007.
I now want to know how the system could be improved using 2010 or 2013.
But first you would need to know our requirements and what we did in 2007 ...
We needed the GUI of My Timesheets and the Admin tasks but approvals based on what project/task it was. Ie PM approval not line management approval.
We managed it by entering timesheets in My Timesheets, importing to My Tasks and then regularly picking up published Task Updates in the Table EPMAssignmentByDay and capturing them in an added table in the Reporting database. We had a few key requirements
which required some customisation:
Need to capture the timestamp of when approved. to nearest hour. plus approver ID (ie status manager) and the cost centre at that time of the resource (they can move sometimes)
Need to be able to freeze approved records - so that after that point they can't be changed. And financial reports can run and know the data won't change.
2 - is a headache for us. There is no mechanism to stop a user from trying to update frozen records. We currently have to just ignore the updates
We also wanted expenses - but that wasn't possible in 2007.
The new "Single Entry" mode looks like it will make life easier for the users.
But:
Is there any concept of timestamping the approvals?
Is there any concept of freezing the approved data?
The new Timesheet user-defined fields. Could these be used to add an expense amount and comment?
I now know my way around the 2007 Reporting Database (at least parts of it) - but haven't found documentation to tell me what changed at the level need to answer the questions above.
Thank you
MikeCro
MikeCro

One of my colleagues pointed me to the MSFT paper "Managing timesheets in Microsoft Office Project Server 2007"
It tells me that there is a field called "Processed" in the timesheet tables in 2007.
It also says "This block is designed to indicate when a timesheet has been transferred to a third-party system.
Customers may also use this field to block the timesheet from being recalled." - which feels like MSFT are trying to give the hooks I need. This could enable me to close off changes - at least at timesheet level if not timesheet line level.
But which field is it in which database table?
I also notice that there is a tantalising comment for one value of the enumeration TimesheetEnum.Status in EPM 2013:
PendingSubmit: Value=5. Pending submission; used when one or more timesheet lines are pending approval after a timesheet is submitted and project manager coordination is required.
This sounds very like it would support what we want: each of the lines in a timesheet week to be approved by the different approvers and then lock the timesheet. (Even better would be to lock a row after PM has approved and a weekly processing
day reached)
Can anyone point me to this level of detail of what is in project Server 2013. or is this in 2010 as well.
MikeCro
MikeCro

Failed to provision site PWA with error: Microsoft.Office.Project.Server.Administration.ProvisionException: To create databases we need dbcreator and securityadmin server roles on servers.

I'm getting the following errors while trying to provision a PS 2010 PWA on our SharePoint 2010 farm. Our PS instance has been working for a while now, and houses two other PWAs. But today,
when trying to create this one, I get "Failed - see the Application event Log" and the following in the Event Viewer:
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Date: 4/2/2014 2:09:08 PM
Event ID: 6980
Task Category: Provisioning
Level: Error
Keywords:
User: DOMAIN\DB_Access
Computer: server
Description:
Provisioning 'PWA/SDN': To create databases we need dbcreator and securityadmin server roles on servers 'DB1' and 'DB1'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{b2178104-1b5b-4c20-8c8f-960678ced9e5}" />
<EventID>6980</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>20</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-02T19:09:08.225Z" />
<EventRecordID>1676727</EventRecordID>
<Correlation ActivityID="{90131653-B0A4-4FAF-A43C-7DF07CBC3332}" />
<Execution ProcessID="11040" ThreadID="12384" />
<Channel>Application</Channel>
<Computer>sharepoint</Computer>
<Security UserID="S-1-5-21-2280669542-4145173436-3058324265-4222" />
</System>
<EventData>
<Data Name="string0">PWA/SDN</Data>
<Data Name="string1">DB1</Data>
<Data Name="string2">DB1</Data>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Date: 4/2/2014 2:09:08 PM
Event ID: 6993
Task Category: Provisioning
Level: Error
Keywords:
User: DOMAIN\DB_Access
Computer: sharepoint
Description:
Provisioning 'PWA/SDN': Failed to provision databases. An exception occurred: To create databases we need dbcreator and securityadmin server roles on servers..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{b2178104-1b5b-4c20-8c8f-960678ced9e5}" />
<EventID>6993</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>20</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-02T19:09:08.225Z" />
<EventRecordID>1676728</EventRecordID>
<Correlation ActivityID="{90131653-B0A4-4FAF-A43C-7DF07CBC3332}" />
<Execution ProcessID="11040" ThreadID="12384" />
<Channel>Application</Channel>
<Computer>sharepoint</Computer>
<Security UserID="S-1-5-21-2280669542-4145173436-3058324265-4222" />
</System>
<EventData>
<Data Name="string0">PWA/SDN</Data>
<Data Name="string1">To create databases we need dbcreator and securityadmin server roles on servers.</Data>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Date: 4/2/2014 2:09:08 PM
Event ID: 6958
Task Category: Provisioning
Level: Error
Keywords:
User: DOMAIN\DB_Access
Computer: sharepoint
Description:
Provisioning 'PWA/SDN': Database provisioning failed.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{b2178104-1b5b-4c20-8c8f-960678ced9e5}" />
<EventID>6958</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>20</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-02T19:09:08.225Z" />
<EventRecordID>1676729</EventRecordID>
<Correlation ActivityID="{90131653-B0A4-4FAF-A43C-7DF07CBC3332}" />
<Execution ProcessID="11040" ThreadID="12384" />
<Channel>Application</Channel>
<Computer>sharepoint</Computer>
<Security UserID="S-1-5-21-2280669542-4145173436-3058324265-4222" />
</System>
<EventData>
<Data Name="string0">PWA/SDN</Data>
</EventData>
</Event>
Log Name: Application
Source: Microsoft-SharePoint Products-Project Server
Date: 4/2/2014 2:09:08 PM
Event ID: 6971
Task Category: Provisioning
Level: Error
Keywords:
User: DOMAIN\DB_Access
Computer: sharepoint
Description:
Failed to provision site PWA/SDN with error: Microsoft.Office.Project.Server.Administration.ProvisionException: Failed to provision databases. ---> Microsoft.Office.Project.Server.Administration.ProvisionException: To create databases we need dbcreator and
securityadmin server roles on servers.
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureDatabases(ProjectProvisionSettings provset, SPSite pwaSite, String adminName, String adminEmail, ProjectDatabaseStateType& originalDatabaseState, Guid& adminGuid)
--- End of inner exception stack trace ---
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureDatabases(ProjectProvisionSettings provset, SPSite pwaSite, String adminName, String adminEmail, ProjectDatabaseStateType& originalDatabaseState, Guid& adminGuid)
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{b2178104-1b5b-4c20-8c8f-960678ced9e5}" />
<EventID>6971</EventID>
<Version>14</Version>
<Level>2</Level>
<Task>20</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2014-04-02T19:09:08.226Z" />
<EventRecordID>1676730</EventRecordID>
<Correlation ActivityID="{90131653-B0A4-4FAF-A43C-7DF07CBC3332}" />
<Execution ProcessID="11040" ThreadID="12384" />
<Channel>Application</Channel>
<Computer>sharepoint</Computer>
<Security UserID="S-1-5-21-2280669542-4145173436-3058324265-4222" />
</System>
<EventData>
<Data Name="string0">PWA/SDN</Data>
<Data Name="string1">Microsoft.Office.Project.Server.Administration.ProvisionException: Failed to provision databases. ---> Microsoft.Office.Project.Server.Administration.ProvisionException: To create databases we need dbcreator and securityadmin
server roles on servers.
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureDatabases(ProjectProvisionSettings provset, SPSite pwaSite, String adminName, String adminEmail, ProjectDatabaseStateType& originalDatabaseState, Guid& adminGuid)
--- End of inner exception stack trace ---
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.EnsureDatabases(ProjectProvisionSettings provset, SPSite pwaSite, String adminName, String adminEmail, ProjectDatabaseStateType& originalDatabaseState, Guid& adminGuid)
at Microsoft.Office.Project.Server.Administration.PsiServiceApplication.CreateSite(ProjectProvisionSettings provset)</Data>
</EventData>
</Event>
Anybody ever get any events like this before? I'm not finding much or nothing on Google or on other forums, so I thought I would run it past and see if anyone has experienced anything of a similar
nature. And yes, the farm account obviously has creator/secadmin permissions, at this point of our deployment....
I look forward to any and all feedback. Thanks and good afternoon!

I figured out the answer to this myself. For those few who might run into something akin to my error...
During the off-hours of where I work, I re-applied the farm account credentials to all dB server VM SQL services that had the account for a log-on (i.e., MSSQLSERVER, SQLSERVERAGENT, etc.) as well as all SharePoint services on our WFE/App Server VM (a two
server farm is what we host), in that order. Then I rebooted the dB server first, followed by the SharePoint server. Upon coming back, everything was working fine again. I was able to provision a site, no probelm, and it seemed to even be a little snappier
when doing so.
One note: doing this procedure gave me a "One or more services have started or stopped unexpectedly" error in the Health Analyzer, for the SPTimerV4 service. When you get this, simply enter into the item and click on "Reanalyze Now;" this will quickly clear
the error out of the Analyzer, and all should be right with the world! :)

TS1814 I have purchased iPhone 3g device from my friend, I connected it to the iTunes to upgrade from 3.1 to 6.0 as many softwares were not being installed as iOS was not up to date. I upgraded but now I can not activate my device. What I should do now???

I have purchased iPhone 3g device from my friend, I connected it to the iTunes to upgrade from 3.1 to 6.0 as many softwares were not being installed as iOS was not up to date. I upgraded but now I can not activate my device. What I should do now??? i am really feeling difficulty because i have been disconnected from the network.
I am from Pakistan.

The 3G cannot be updated to iOS6, it can only go to iOS 4.2.1.
Activation issues are generally the result of the device being hacked or jailbroken.

Parser Error Message: Could not load file or assembly 'Microsoft.Office.Access.Server.UI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies,

Dear All,
I have installed Sharepoint Foundation 2010 in my server 2012 R2 machine. and I restore my existing content database backup into new site collections. and I'm trying to browse the site collection in window, the below error shown..
Parser Error
Message: Could not load file or assembly 'Microsoft.Office.Access.Server.UI, Version=14.0.0.0,
Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies.
<add assembly="Microsoft.Office.Access.Server.UI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
I tried to checked the assembly folder having the DLL or not. but its
not available in the C:\Windows\assembly location. and I'm tried to resolved this issue by HOTFIX. but unfortunately, I can't find out the patch file for MOSF 2010 in server 2012 r2.
Please help me on this issue. I'm very new to sharepoint...
Any help will be more appreciated.
Thanks,
Mubarak

Hi Mubarak,
Please firstly make sure you installed SharePoint Foundation 2010 with SP2 in a Windows Server 2012 R2. Since only SP2 slipstream installations are supported on Windows Server 2012 R2
http://blogs.technet.com/b/stefan_gossner/archive/2014/05/03/sharepoint-2010-sp2-and-windows-server-2012-r2.aspx
http://blogs.technet.com/b/stefan_gossner/archive/2013/09/19/slipstream-version-of-sharepoint-foundation-2010-with-sp2-included.aspx
Regards,
Rebecca Tu
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Vbscript Execution in Microsoft Office Communications Server 2007 Speech Server.

I am trying to add a Speech Server Application through Code using Vbscript in Microsoft Office Communications Server 2007 Speech Server. Below is Vbscript.
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\MSSV2")
Set objPeerClass = objWMIService.Get("Application")
Set objPeer = objPeerClass.SpawnInstance_()
objPeer.Name= "ApplicationOne"
objPeer.Put_
wscript.echo "Created Application= " & objPeer.Name
Above Script gives Error Number 80041031. Please help me to remove this Error.

Here are the docs for scripting Speech Server:
http://msdn.microsoft.com/en-us/library/bb800709(v=office.12).aspx
Example:
' Get MSS object on specified host
strHostname = "."
Set objMSS = GetObject("winmgmts:\\" & strHostname & "\root\MSSV2:MSS=@")
' Print configuration summary
For Each p in objMSS.Properties_
If p.IsArray Then
If isNull(p.Value) Then
Wscript.Echo p.Name, "="
Else
Wscript.Echo p.Name, "=", Join(p.Value)
End If
Else
WScript.Echo p.Name, " = ", p.Value
End If
Next
objMSS.Properties_("ShutdownTimeout")=300
'Update WMI with a modified instance
objMSS.Put_
Post future questions to Speech Server (Office Communicator) forum.
¯\_(ツ)_/¯

Since upgrade from Exchange 2007 to Exchange 2013 the conversations in Outlook do not group by subject

Hi Microsoft,
Since we have upgraded from Exchange 2007 to 2013 users complain their conversations in Outlook are no longer grouped based on the subject of an e-mail. I looks like Outlook uses other message properties for grouping e-mails in a conversation.
I have investigated all the forum topics and see that with exchange 2010 there is support added for the use of conversation-ID's. However the functionality to automatically group e-mails with the same subject in one conversation in Outlook is gone!
I would like to know if there is a fix to implement so that some our users get this functionality back. For Example: Let the exchange server not generate conversation-ID's and message-ID's for certain users.
Your help is greatly appreciated!

Totally correct!
If you don't plan to maintain Outlook then you plan to fail :(
Additional links etc are in here:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Upgrading from Exchange 2007 to Exchange 2013

Hi There,
I have two exchange serveres 2007 SP3 and they are ruining on Server 2008 Ent and 2008 R2 Ent.
I setup a server 2012 R2 and installed an exchange 2013 on it and a friend of mine helped me on setting up the new exchange server and migrating the mailboxes.
Now all the mail boxes are transferred to the 2013, and based on his recommendation I am in the stage of uninstalling exchange 2007 from my old servers.
I am reading about the process but based on the link below I have to do more things before uninstalling
http://www.exchangedictionary.com/articles/clean-uninstallation-of-exchange-2010-mailbox-server-guide
the instruction is for exchange 2010 and some shell commands are not working on shell 2007
I also found the link below:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
and I think I am at the stage 8 or 9, but I am not sure and also I do not know what to do if I am at the stage 8
Would you please advise me what shall I do to finish up the project or give me a link for it.
I have searched a lot but I was not able to find a straight forward instruction.
Thank you in Advance

Hi MAS,
Thank you for your reply
I found the instruction below:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-4-step-by-step-exchange-2007-to-2013-migration.aspx
but I am not sure if I am in the step of moving public folders or not. I have finished the migration of all mailboxes.
When I click on "Servers" I can see the results below:

Best Way to move MB database from single XCH 2010 to 2013 DAG

Hi,
We are migrating from a Single Exchange 2010 sp3 server to a 2-node exchange 2013 DAG cluster, located in another AD site.
I can move a mailbox from 2010 to 2013 without issue, but the WAN link between 2010 and 2013 is very small.
It will take us too long to move all mailboxes with move-mailbox over the line.
Is there another way to move the mailboxes or Databases more quickly?
I was thinking about copying the DB's to a physical disk from 2010 and then move and mount it on 2013. Is that even possible? I explored the possibility to seed the DB to 2013, but don't have the option to do so. 2010 is installed on 2008R2 standard.
We prefer a short downtime and move over everthing in one go as opposed to having coeexistance for longer period of time to allow the move mailbox over the WAN to complete.
Thanks for any suggestions.

You can't move the databases from Exchange 2010 to Exchange 2013.
I can think of three options.
1. Move the Exchange 2013 server to the same LAN as the Exchange 2010 server, move the mailboxes, then move the server back.
2. Move the Exchange 2010 server to the same LAN as the Exchange 2013 server and move the mailboxes.
3. Install a new Exchange 2010 server on the same LAN as the current Exchange 2010 server, create a DAG, add mailbox database copies on the new Exchange 2010 server, move that server to the same LAN as the Exchange 2013 server, activate the databases
on that LAN, and then move the mailboxes.
3a. A variation of #3 is to build the Exchange 2010 server on the same LAN as the Exchange 2013 server and perform a manual seed of the database copies. This is more trouble than option 3.
Moving Exchange servers between sites is possible but there are other issues you would need to solve. You might be best off just getting a temporary increase in your WAN link capacity for the period of the mailbox move.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Workflow status web part gives error when going back to previous stage (using GO TO) in Project Server 2013 workflow

Hi,
Workflow status web part gives error when going back to previous stage (using GO TO) transition activity in Project Server 2013 workflow.
Please guide how to create a workflow which restarts from a desired stage.

Thanks for your prompt reply....
It gives following error
Workflow Status
This Web Part was unable to load.
Information that may be useful in solving this problem was written to the Unified Logging Service (ULS) log on the Project Web App with the following ID: e95a9c9c-1f68-90d7-0a3e-5951df70fec6
For more information, contact your Project Web App administrator.
what do you mean to restart the Project Server 2013 with different project name, please elaborate....

Registry keys after SharePoint Upgrade from 2007 to 2010

Hi,
I'm working on a SharePoint Server 2010 Farm, where it has been upgraded from 2007, actually I don't have enough information about the history of this upgrade, but
it seems it was an in-place upgrade, and the 12 Hive folder is still there.
Looking at the Windows Registry, I found that Registry Entries for 2007 version is still there: ([HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared
Tools\Web Server Extensions\12.0] ), one of those entries is named "SharePoint" and its value is "Installed".
Is this a normal situation?
We are trying to install an antivirus for SharePoint but the installation is keep failing the vendor is claiming that this is the issue (2007 registry entries), and
that the upgrade have not been done successfully.
The SharePoint 2010 farm is running perfectly, and I have ran a "LocalUpgradeStatus" command on one of the servers, the output is with no issues.
I have checked below pages and everything is normal:
Check product and patch installation status
Review database status
Check upgrade status
Any thoughts? is it normal to have such old registry entries in place? shall I just clean them?
What do you recommend in such situation?
Hamza AlSughier

Hi Hamza,
It should be in-place upgrade for your environment, here is a workaround per the following similar post, please confirm with antivirus vendor if the 12 registry files and 12 hive cause this issue, if yes, then backup the 12 registry files and 12 hive, then
after you installed the antivirus successfully you can add the keys back.
Note, Please fully test in your testing environment firstly before touching the production, and production also needs to be fully backed up.
https://social.technet.microsoft.com/Forums/en-US/0a3f0b25-49be-488c-ac11-0bfab0f3cbe1/do-you-recommend-remove-sharepoint-2007-after-upgrade-in-place-to-sharepoint-2010?forum=sharepointadminprevious
Thanks
Daniel Yang
TechNet Community Support

Lync server 2010 and 2013 coexistence replacing edge servers

Hi all,
here is Our current deployment:
Lync server 2010:
1 edge
1 FE
3 branch sites
1 Monitoring server
Lync server 2013:
3 FrontEnd
2 Edge
2 Mediation
3 Backend
Simple urls are still point to Legacy (2010) servers.
External settings of Edge 2013 servers have been define With different name (Access,WEB and AV) and DNS (internally and externally) is pointing to New 2013 servers (via KEMP and TMG).
ATM 2013 topology is using edge2010 server.
Seems like we have two options for replacing Edge servers,one is Rip and replace and the other one is side by side transition.
We would like to do rip and replace so we can keep old simple urls (so that we dont have to send notice to external partners about Our New Access edge info) and using 2013 edge servers for federation and keep users on 2010 servers,then move them in
a controlled way.
What is the best way to do this?
Thanks!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Hi,
From your description above, the purpose is no need to update the New Access Edge info to the external partners. So for those external partners who set federation type of “Allowed Partner Server”, you need to keep the SIP domain name and the Edge Server
FQDN the same as before.
So base on my knowledge, you need to plan a down time, and firstly cancel the federation route for the Lync Edge 2010 Server. Delete the Lync Edge 2010 Server and publish the topology. Then deploy the Lync 2013 Edge Server with the same FQDN with Lync Edge
2010 Server. Then enable federation for it and point to the Lync Server 2013 FE Pool.
Best Regards,
Eason Huang
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Eason Huang
TechNet Community Support

8.1 upgrade from 8.0 and Outlook 2013

MS Office Outlook worked perfectly well until I upgraded from Windows 8.0 to 8.1. Error message reads "MS Outlook has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution
is available." The only option is to close the program.
Also, screen brightness no longer is adjustable (and it is too dim for my liking): I cannot make it brighter or darker!
I reinstalled and both error message and lack of brightness control persist.
cliff

Hi,
For the brightness issue, please try to update your graphics driver first, this is a common issue for those who had their OS upgraded to Windows 8.1. (Device Manager ->Display adapters)
Regarding the Outlook error, if update the graphics driver doesn't fix the issue, it could be that an issue with data file is preventing Outlook from starting correctly.
I would suggest you to use scanpost.exe to scan your data file for errors.
Please refer to this article on how to use scanpst.exe:
http://office.microsoft.com/en-us/outlook-help/repair-outlook-data-files-pst-and-ost-HA102749454.aspx
Or create a new mail profile in Outlook and have a try:
http://office.microsoft.com/en-us/outlook-help/create-an-outlook-profile-HA102749460.aspx
Thanks,
Ethan Hua CHN
TechNet Community Support

Upgrade from 2005 express to 2008 r2 express - provisionsystemaccounts.sql error

Hi,
I’ve been upgrading several of my clients and ran into this problem for one of them.
When doing the upgrade I got..
Looking at the error logs indicated..
2015-03-21 11:54:07.58 spid7s
Database 'master' is upgrading script 'provisionsystemaccounts.sql' from level 0 to level 2.
2015-03-21 11:54:07.59 spid7s
2015-03-21 11:54:07.59 spid7s
Starting provisionsystemaccounts.sql ...
2015-03-21 11:54:07.59 spid7s
2015-03-21 11:54:08.02 spid7s
Error: 15151, Severity: 16, State: 1.
2015-03-21 11:54:08.02 spid7s
Cannot find the user 'FILESERVER01\SQLServer2005MSFTEUser$FILESERVER02$ORSQLEXP', because it does not exist or you do not have permission.
2015-03-21 11:54:08.03 spid7s
Error: 912, Severity: 21, State: 2.
2015-03-21 11:54:08.03 spid7s
Script level upgrade for database 'master' failed because upgrade step 'provisionsystemaccounts.sql' encountered error 15151, state 1, severity 16. This is a serious error condition which might interfere with regular operation and the database will be
taken offline. If the error happened during upgrade of the 'master' database, it will prevent the entire SQL Server instance from starting. Examine the previous errorlog entries for errors, take the appropriate corrective actions and re-start the database
so that the script upgrade steps run to completion.
2015-03-21 11:54:08.03 spid7s
Error: 3417, Severity: 21, State: 3.
2015-03-21 11:54:08.03 spid7s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how
to rebuild the master database, see SQL Server Books Online.
2015-03-21 11:54:08.03 spid7s
  SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.Running the Repair from the Installation centre
brings up the same error.
I noticed that the instance appears to be upgraded but basically the service won’t run. I can start it but it just stops again.
So I found this which seems the same as my problem..
https://ilkirk.wordpress.com/2011/03/07/in-place-sql-upgrade-error-2005-to-2008/
Even though I can start the SQL Services using point 1 from the link above I can’t connect to sql using DAC.
The sqlcmd won’t work and trying to connect through SSMS.
> SQLCMD –E –A. I’ve also tried >SQLCMD FILESERVER1\ORSQLEXP –E –A and get the same results
HResult 0xFFFFFFFF, Level 16, State 1
SQL Server Network Interfaces: An error occurred while obtaining the dedicated administrator connection (DAC) port.
Make sure that SQL Browser is running, or check the error log for the port number [xFFFFFFFF].
When I try to connect to DAC via SSMS I get ..
So I seem to currently have 2 problems, one using sqlcmd/DAC and the other with provisionsystemaccounts.sql.
The sqlbrowser is running but from 90 (not sure if that matters) and I have removed (following online research) the 80 and 90 binn settings from the PATH just leaving 100 but this hasn’t changed the errors.
I’ve tried enabling DAC using this advice below but it hasn’t made any difference. The service keeps stopping and no SQLCMD action.
http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
So after trying numerous options I currently stumped.

An update to this. I can now DAC via sqlcmd.
Following the advice on
[url]https://ilkirk.wordpress.com/2011/03/07/in-place-sql-upgrade-error-2005-to-2008/[/url]
I'm at point 3
3.Issue a ‘create login’ command to create the user / group you’re missing, followed by the all important GO
and I'm a bit unclear on what to do. The user according to the error log is 'FILESERVER01\SQLServer2005MSFTEUser$FILESERVER02$ORSQLEXP'
and I tried
>sp_addsrvrolemember 'FILESERVER01\SQLServer2005MSFTEUser$FILESERVER02$ORSQLEXP', 'sysadmin'
>go
adding this seemed to work without error but running the repair from the installation centre bought up the exact same error as before.
So, bearing in mind using the advice from the above link
Have I added the user to the correct group?
If not how do I do that?
In the advice he also mentions..
Now – why did this happen? Well, in my situation it seems to be related to the fact that I upgraded the default instance first which also upgraded the Full Text Engine. That, in turn, removed the Full Text Engine user group from the local groups.
In particular, I was missing “<ServerName>\SQLServer2005MSFTEUser$<ServerName>$MSSQLSERVER”. Note the fact that it mentions the default instance, not the named instance!
The SQLServer2005MSFTEUser login refers to a local Windows group that is used for controlling access to the Full Text Engine. I suspect that when I upgraded the default instance, the installer removed the group from Windows, but not necessarily
from the named instance of SQL. Once I recreated the group, granted my service account access to mirror the other similar groups, and added that login back into SQL via the DAC, everything went fine from there.
thanks,

Upgrading from Project Server 2010 to 2013 ConvertTo-SPProjectDatabase gives error (Convertto-SPProjectDatabase : Action 15.0.38.0 of Microsoft.Office.Project.Server.Upgrade.PublishedDatabaseSequence)

Similar Messages

Maybe you are looking for