Fatal error on Premiere Elements 3.02 when loading any project (new ones included)

Has there been any recent reports of problems with 3.0 on Vista? I set up a new project, imported three DV videos totalling 100 minutes. Later, I added two JPEGs and a short MP3. Shortly after the additions, my system completely froze and had to be powered down. When it came back up, PE gave me the "serious error has occurred" message shortly after it loaded any project, even brand news ones that had just been saved. I did a Repair from the Control Panel and then complete CHKDSK overnight, but PE seems to be completely messed up and cannot load any projects. Any ideas?
This is Vista 32 SP2 on a dual-core 1.86 Mhz with 2 gig RAM. Thanks for any input...

"Also, can you confirm that your "DV" videos are DV-AVIs captured over
FireWire from a miniDV camcorder?"
I missed this in my earlier reply. Yes, it was from a miniDV camera,
using firewire. The only other odd thing is that I suddenly had trouble
with the audio and at one point saw a brief Windows driver message about
the 1394 driver being installed. The audio is being routed through a
PreSonus Inspire sound unit that is also connected via firewire.
However, this is a setup that has been working without a problem for a
while (a few years), with PE using the Inspire audio without a problem.

Similar Messages

Premiere Elements 9 crashes when trying to create new project?

I dont seem to be able to get this application to work..... it was fine a few months ago, but when I went to create a new project it continually crashes out when you try and open an existing or new project file.
can anyone suggest a possible rememdy please?\

dudleythedog
What computer operating system is your Premiere Elements 9 running on? And, are you running it from the 9.0.1 Update?
Does the problem exist with and without the antivirus and firewall(s) disabled?
Then the usual
1. Running program from an User Account with Administrative Privileges plus Run As Administrator applied to program's desktop icon?
2. Last version of QuickTime installed on same computer with Premiere Elements?
3. Video card/graphics card driver version up to date according to web site of manufacturer of the card? According to the Device Manager/Display
Adapters, how many video cards/graphics cards does your computer use - 1 or 2?
As a first pass at this, let us delete the Adobe Premiere Elements Prefs file, and, if necessary, the whole 9.0 Folder in which the Adobe Premiere Elements Prefs file exists.
Assuming Windows 7, 8, or 8.1 64 bit computer....
Local Disk C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
9.0
and, in the 9.0 Folder, is the Adobe Premiere Elements Prefs file that you delete. If necessary, delete the whole 9.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the whole path cited.
We will be watching for your results and then decide what next.
Thank you.
ATR

Premiere Elements 8 can't open any project

Hello,
I am running Premiere Elements 8 (fully-paid version) and trying to open a project which I created last night. But I'm finding I can't open any project. On the welcome screen, when I click on "Open Project", I get a pull-down menu (as expected):
But no matter what option I select (even "Open..."), I get the same result: The "Open Project" button turns into a wait-bar for a minute or two:
...and then "Open Project" simply reappears without anything else happening.
I also tried a different approach, going to the .prel file in Windows and double-clicking it. But again, nothing happened.
My PC is running Windows 7 Home Premium. The hardware is a 64-bit, HP p6310y with an AMD Athlon II X4 630 processor, 2.8 GHz, with 6 GB of RAM.
Any suggestions?
- Bruce Romney
Valley Forge, PA

Hello,
I have the exact same problem as you with PE8 and Win7 (x64), and a reboot also helped me. But the problem came back the next time I tried to open PE. Have you expreienced the same? It cant be that we have to reboot every time we want to use PE?
Best regards
Øystein Morvik
Norway

Premiere elements 10 crashes when saving as DVD or DVD folder, etc.

Hi [me again!]
While awaiting resolution for PRE7 and PE7 'registered' licence 'not accepted' problems, my other Premiere elements 10 crashes when saving a Project as DVD 4.7Gb folder or direct to DVD or 'any other DVD way'.
The repeated windows error report I get is this:
Problem signature:
Problem Event Name:    APPCRASH
Application Name:    Adobe Premiere Elements.exe
Application Version:    10.0.0.0
Application Timestamp:    4e791009
Fault Module Name:    wdmaud.drv
Fault Module Version:    6.1.7601.17514
Fault Module Timestamp:    4ce7c9f8
Exception Code:    c0000005
Exception Offset:    000000000000f827
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    2057
Additional Information 1:    c1eb
Additional Information 2:    c1eb94943c7b4efb7ee314d92a94924b
Additional Information 3:    7d3f
Additional Information 4:    7d3fe30533dcbba28d68d00b60422c7b
In the meantime I am evaluating the 'cheaper' and without installing / working / DVD problems and possibly send Adobe discs back for full refund.
My Laptop is fast enough and well kept - not other 'larger' programmes have any problems running or installing [Stenberg Cubase Pro, Flight Simulator X and so on] only Adobe programmes!
I am really getting tired now.
Regards
Mobon

Hello
All problems are carefully separated - not all together, since I am a tidy person by default.
It is very simple and not confusing.
I actually have one main issue with PE7 and PPE7 [which I hope they will care of] and a series of small teething problems as many in these forums have on Premiere 10 since installation because Adobe programmes have 'basic' problems even loading / reading/ converting its own created files.
I looked up for Premiere Elements problems on-line [on external forums] and I can see so many problems and people opting for alternative programmes or getting 2 or 3 different programmes to do the job faster and better - that confirms my thoughts.
I am not here to stir things up [if by any chance you are thinking that], but I am merely trying to use a PAID and SUPPOSED to be GREAT program and it is clearly not my friend.
But if I get pushed up around and treated like a non-in-the-computer-field-person, then I might 'need to' stir things up with 'proves'!
I have been working with computers Hardware and Software since 1975 with the Sir Sinclair Spectrum .
So, I do know one thing or two by working 'manually' and without the 'easy' mouse clicking [!] and my main job these days is to actually fix People's messed up computers, recover data, erase data, etc. and often I find either Apple's or Adobe's programmes not working properly [being the main problem on slower computers] and users tried to fix them and messed things up!
Mainly is Apple programmes [ iTunes is one!] on Windows environment - just pure mess.
In fact I do not keep ANY Apple Programs on ANY my computers any-more and by adding the blooming QuickTime - it actually adds 3 'mostly not needed' applications that must be run in the background only slowing down 'most standard' computers and 'mostly' for no apparent reason but needed by Premiere Elements 10.
Adobe Acrobat Reader too is a kind of an offender in that sense, which I do not use any-more in favour of an alternative and very light program that does not invade your computer.
I could be talking about the above for days ...
The fact I do not know Premiere 10 very well and I am having some teething problems with 'Adobe Premiere Elements 10' does not make me a lower being or anything to the like or even put me aside the forums for being realistic and a human being most of all.
I simply am an Intermediate / Advanced / Professional Computer User / Repairer [depending on which subject] trying to fix this non-working-properly Adobe's program and get on with his life.
You as an employee perfectly know what I am talking about, the Adobe numerous problems with Elements and pro and the clever Marketing and money making tool Adobe has created around it and I do understand you must keep Adobe's side - of course and that is not a problem at all.
BACK TO THE ONLY PROBLEM THIS THREAD IS OPEN FOR:
Having said that, in the meantime I seem to have solved it myself [as I do most of the time], at least for now.
I am sure many other problems will arise.
My Solution that worked:
I simply clicked on the time-line [bottom] and then clicked on top menu TIME-LINE [if I am not wrong, it was late night and I might be wrong - do not crucify me please!] and MERGE CLIP and then I let the program do the job I purchased for.
Days ago using the Trial Version [before I purchased Premiere 10] I already read that Premiere does not like either large gaps [I did not have] or even simple clip cuts not merged and it did have 'loads' of problems, but most of them were solved by 'users' mostly.
Anyway, that seems to have done the trick, even thou it did take around 4/5 ours to do 3Gb ! Why?
My computer is fast.
But I have not checked or burned the files yet - so, I do not know100% - just yet, I will check later on today.
I believe Adobe must prepare a Service Pack with 'Loads' of fixing, there is no place to hide and that may convince users to even 'spend' and buy the PRO version - the ball is in your court now.
I cannot believe Premiere is having so many small teething problems and I am only doing a BASIC test and I can see the vast majority of users of Elements Programs going literally insane and only us, the more Techy ones coping.
Regards
M
PS the fact you see an avalanche of problems with my installation is actually normal.
That is because I am a 'fast' and organised Computer Technician which gets on with things and I usually do this with all new programmes to get rid of the possible initial several small hiccups, that other Companies usually fix with Patches - not Adobe, it seems - at least with Premiere elements.
In the last few years are mainly with Adobe Programmes. It is the only way to get the 'basic' program problems fixed straight away, so I do know the next time I run it actually works!
ADDITION:
IT WORKS!
Message was edited by: mobon

Help! Premiere Elements 7 won't load project

Premiere elements 7 won't load my project. Icon just spins - for about 10 minutes - then it freezes. Figures that I am so close to finishing!!! What are my options? Can I copy the project and open on another computer? Can I download a newer version of Pre and upload the unifinshed project?? Any help is greatly appreciated!!

Welcome to the forum.
Unfortunately, PrE does not offer that many options, if a Project goes "off."
However, these would be my first steps, and pretty much in this order:
Go to the PrE AutoSaves, and change the View to Details, so you can see the Dates/Times. Try Opening the very latest one. Note: if you have not changed the default, there should be five AutoSave files, and they should be located in the PrE AutoSave folder, in the Project's heirarchy. You want the latest one, not the one with the highest increment. AutoSave 03 could be newer, than AutoSave 05.
If that does not work, then try this - Move your Assets to a new location. Then, Open your original Project. As it loads, you should be presented with "Where is file _____?" and that is what you want.Here is the tricky part. If you have many Assets, and hopefully they are in the same folder, or a few folders, and not spread around the system. I would move all Video Assets to a Video folder, all stills to a Stills folder, all Audio to an Audio folder, etc. as you want to isolate things. When presented with the "Where is file ____?" navigate to the folder with that file, and locate it. PrE will then relink to all used Assets in that folder. This is why I would segregate Assets by type, to isolate the problem, if possible. If all of your Video files load fine, you will get a "Where is file ____?" for the stills, or the music, and repeat. If the Project fails on one Asset type, then you have located the bad Asset by type, and can repeat the exercise, by segregating each file in that Asset type, to a unique folder, navigating to each folder, when prompted, until you find the bad Asset.
In the tests above, never do a Save, but only a Save_As, so as to not overwrite the original PREL file.
Good luck, and hope that it is a bad Asset, and nothing more.
Hunt

Error Installing Premiere Elements 9 - Exit Code 7

Hi, I'm trying to install Premiere Elements 9 on a Mac (running 10.6.4), but it always comes up with an error, and the program can't be installed. Last time I tried it got to about 95% but then gave me this error:
Exit Code: 7
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 3 error(s), 3 warning(s)
WARNING: Payload cannot be installed due to dependent operation failure
WARNING: File/Folder does not exist at /Volumes/PRE9 PSE9/Adobe Premiere Elements 9/payloads/AdobeElements9Organizer/oem/ols
WARNING: Payload cannot be installed due to dependent operation failure
ERROR: The following payload errors were found during install:
ERROR: - Adobe Premiere Elements 9_LangPacken_US: Install failed
ERROR: - Adobe Premiere Elements 9: Failed due to Language Pack installation failure
I've tried this four or five times, and I always get exactly the same error. The only help the installer offered was "Please try restarting your system and try again." and all I could find on Adobe Support was "Install under Safe Boot Mode", which I tried, and it still failed.
Does anyone have any ideas whatsoever as to what I can do to actually get this installed?
Thank you very much in advance, anyone who can help!

I've never seen so many error codes related to language, jobbo! That's very strange.
Meantime, I've loaded Premiere Elements and run it on a couple of Macs, and it usually loads right up and runs beautifully. There does seem to be a conflict with Bridge sometimes, but I'm not sure if that's the case here or not.
It might be worth contacting Adobe's tech support. (You find contact information under the Contact button at the top of this page.) And, when you do, ASK FOR A MANAGER, don't just talk to whoever answers the phone. Most of the guys on the phones are just working from scripts and KB articles. If you can get a manager on the line, he and she will work through your unique situation.
Meantime, I'll keep my eyes open for solutions.
(BTW, I'm assuming you're using at least OSX 10.4 on at least a dual-core Intel processor.)

Premiere Elements 9 crashes when I try to open a project

Premiere Elements 9 was installed on my laptop when I bought it. I have only just tried to use it for the first time this week. When I choose 'create a new project' it opens but there's only a blank screen - no way to start editing, drag video in, etc. When I try to re-open a project, it crashes - saying there has been an error and it has to close.
I have uninstalled and re-installed from the discs that came with the laptop but this problem continues to happen.
Any ideas what I can do to fix this?
Thanks.

Thanks for your suggestions. I'm working on a Windows 7 laptop.
When I try to download the 9.0.1 update I get an error message: "There was an error downloading this update. Please quit and try again later". It doesn't say what the problem is.
1. Yes
2. I've tried this and got the same blank grey screen as before (no work area) - tried to open a project/ create new and I got the error message: "Sorry, a serious error has occurred that requires Adobe Premiere Elements to shut down." But then it doesn't shut down.
3. I'm not sure what kind of video card - how do I find this out?
Unless you have other suggestions, given my replies above, I'll try deleting the folder you suggest next.
Thanks
Emily
Premiere Elements 9 crashes when I try to open a project
created by A.T. Romano in Premiere Elements - View the full discussion
emilyw76
What computer operating system is your Premiere Elements 9 running on? For now I will assume Windows 7, 8, or 8.1 64 bit.
Have you installed the 9.0.1 Update and are trying to work from it? I suspect not. To do that, you can use Help Menu/Update within the project or, if that is not possible, you can do the update with the program closed. Use the download link
Adobe - Premiere Elements : For Windows : Premiere Elements 9.0.1 update
Then the usual
1. Do you have the latest version of QuickTime installed on your computer?
2. Are you running the program from a User Account with Administrative Privileges and have you applied Run As Administrator to the desktop icon of the program?
3. What video card/graphics card does your computer use? How many cards, 1 or 2? And, is the card driver version up to date according to the web site of the manufacturer of the card or the web site of the manufacturer of the computer?
An important troubleshooting scheme is to delete the Adobe Premiere Elements Prefs file and, if necessary, the whole 9.0 Folder in which the Adobe Premiere Elements Prefs file exists.
Local Disk C
Users
Owner
AppData
Roaming
Adobe
Premiere Elements
9.0
and in the 9.0 Folder is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then you delete the whole 9.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the complete path cited.
After you determine that the video card/graphics card is up to date and the problems persist, the delete the BadDrivers.txt file.
Local Disk C
Program Data
Adobe
Premiere Elements
9.0
and in the 9.0 Folder is the BadDrivers.txt file that you delete. (After you close out of there and open a project, a new BadDrivers.txt file will be generated but the problem should be gone hopefully.)
Please review and consider the above and then we will decide what next as indicated.
Thank you.
ATR

Trying to install Adobe Premiere elements 12. When it gets to "Installing required Shared Technologies" stage it gives errror "Setup has detected that Adobe Bridge CS5 (Bridge.exe) is currently in use. Please close all running exe(s). Nothing is runnin

question: Trying to install Adobe Premiere elements 12. When it gets to "Installing required Shared Technologies" stage it gives errror "Setup has detected that Adobe Bridge CS5 (Bridge.exe) is currently in use. Please close all running exe(s). Nothing is running when trying to install this, have been through this process several times. Found undertroubleshooting to delete files PDAppFlex.swf and PDAppFlex-app.xml and have done that as well. Any help will be greatly appreciated

Try Error "Installation cannot continue until... Adobe Bridge is closed" | Installation | CS5

Premiere Elements 7 crashes when I start to edit clips

I have downloaded Premium Elements 7 and installed same. I have taken a small series of 12 clips to try the software, into "new project (all 12 clips).
I then took the clips into the editing mode, but after dragging the 3 clips the programme crashed.
This has happened several times. Each time a menu pops up and says "Adobe has stopped working. A problem has caused the programme to stop working correctly. Windows will close the programme and notify you if a solution is available. CLOSE."
I have Vista Home Premium, using a 2GB dual core intel with 160 GB harddrive. Can some one tell me what is wrong please

Dear Steve,
Thanks for the prompt response. I am having major problems. As you suggested I activated quicktime and then updated this. Then my problems got worse as I was unable to find the clips which were originally stored in Adobe photoshop so could not obtain them. I decided to uninstall PREMIUM ELEMENTS and re-download after restarting my PC. Unfortunately it will not install. it aborts part way throughthe installation
Install shows, C:\Program files\Adobe\Adobe Premiere Elements 7.0\ then Next, then Install, which I click on.
Part way through this install procedure a menu appears
Menu Error 1311. Source file not found and C:\User\Admin\App Data\Local\Temp\wzde 24\data1.cab. Verify that file exists and that you can access it. Retry and cancel
Checking through the files the last one is wzde 24 but no data1.cab file.
So what else am I not doing or doing wrong.
Thanks for your assistance
Barry
PS I have 23 GB on C and a full 69 on D
Video is a Sanyo Xacti an MP4 system
Downloaded with still pictures to Adobe Photoshop and then Pics into one folder and videos into another folder and to sub folders
Date: Tue, 26 May 2009 09:42:35 -0600
From: [email protected]
To: [email protected]
Subject: Premiere Elements 7 crashes when I start to edit clips
1) What are you using for source files? Photo? Video? If video, what type of camcorder did the video come from and how did you get it into your computer?
2) How much free, defragmented space is on your hard drive?
3) Is your operating system up to date? (Manually going to Windows Update and adding the hidden or custom updates) Do you have the latest version of Quicktime -- which is critical for running this program with any stability (per the FAQs to the right of this forum)? This is particularly important when running Vista.
http://forums.adobe.com/thread/416585?tstart=0
>

Runtime error in Premiere elements?

runtime error in premiere elements

uvagreg11
You will need to supply a lot more information than just "runtime error in premiere elements" in order for us to help you.
1. What version of Premiere Elements are you using and on what computer operating system is it running?
2. What are you using a the project preset for your project? And, what are the properties of the source media that are being used on the Timeline?
3. Is this a "it worked before but now" or "it never worked before" type of problem?
4. What is the description of your computer and its resources?
5. What troubleshooting have you done so far...
a. flushing preferences
b. deactivation, uninstall, reinstall
c. other
The following is an Adobe document on run time error troubleshooting.
http://helpx.adobe.com/x-productkb/global/troubleshoot-c-runtime-errors-products.html
Let us start here and then decide what next based on your details.
Thanks.
ATR
Add On..I did not see SG's post until after I had posted mine.

I am trying to use my adobe premiere elements 12 and when I go to click on a "new project" it takes me to the sign in page. Once I type my information in and click on "sign in" a little 'thinking circle' pops up and it just keeps spinning

I am trying to use my adobe premiere elements 12 and when I go to click on a "new project" it takes me to the sign in page. Once I type my information in and click on "sign in" a little 'thinking circle' pops up and it just keeps spinning but it never ends up doing anything. Please help me with this issue. I really need to get this project started like yesterday. Thank you.

dplum12
What computer operating system is your Premiere Elements 12 running on? Did you have the opportunity to update 12 to 12.1 Update yet using an opened project's Help Menu/Update? If not, please do so when you get the opportunity.
For now I will assume that your computer is Windows 7, 8, or 8.1 64 bit. Please try the following suggestions to overcome your Premiere Elements Sign In issue.
http://www.atr935.blogspot.com/2014/04/pe12-premiere-elements-12-editor-will.html
and, if you get any messages about Internet connect and the computer clock, please review the following
http://www.atr935.blogspot.com/2014/04/pe12-sign-in-failure-connect-to.html
Please let us know the outcome.
Thank you.
ATR

I purchased Adobe Premiere Elements 13. When I try to log on, I receive a message "Invalid serial #"

I purchased Adobe Premiere Elements 13. When I try to log on, I receive a message, "Invalid Serial #". Please help.

Make sure you have cookies enabled and clear your cache. If it continues to fail try using a different browser.

Premiere Elements 8 won't load recently saved project

I'm using Adobe Premiere Elements 8 to create a highlight video. I made two videos last year and didn't have this problem but this video is slightly longer. About twenty minutes total consisting of approximately 100 video clips. I've added one more group of clips and not when I try to load the saved project I just get a gray blank screen. The load message finishes but nothing appears. The drop down menus are mostly still grayed out. No good selections except to press load project again. This causes a system error that shuts down the application. Any tips or tricks are appreciated.
Thanks,
Dave Flick

Bill, here is the good news.
I updated the Quick Time like you suggested but no help. I updated the video driver but no help. I disabled the hardware acceleration but no help. During this time I realized the problem started after I upgraded McAfee. I remembered the new McAfee Real Time scanning effected my Outlook software. So I disabled the McAfee Real Time scanning and then Premiere Elements 8 would successfully load my saved project. What a relief. I went back and Turned On the McAfee Real Time scanning but changed the setting to only scan programs and documents, not all files as previously set. I'm back in business and really appreciate your help. Thanks a million.
Dave Flick

Error:The grouping element could not be determined for project

Hi,
When I am trying to issue goods for a project,I am getting the following error
"The grouping element could not be determined for project 1., plant 2., and MRP group 3.."
what may be the reason for this reason.
Regards,
Raju

Hi,
You are using Automatic Requirement Grouping in your project and there is some issue with the Material Master,please check the Material Master Views.
Muzamil

Fatal Error: The schema version of the database is from a newer version of WSUS

Hello,
CM2012 R2 RTM on Server2012 R2 RTM with SQL2012 SP1
installed SQL, WSUS and then CM.
When finished adding WSUS, there was a post installation message but I skipped it and continued to CM installation, as suggested on some blogs. WSUS in CM seems to be a real mystery... and there are multiple workarounds and suggestions.
Now my CM is ready to GO. Configured discovery, boundaries. All components appear green OK. My hand shaked when I click on post Deployment message related to WSUS in server manager. So I clicked it. And received: Post Deployment Failed. There is
a path to log file. The error:
Fatal Error: The schema version of the database is from a newer version of WSUS
than currently installed. You must either patch your WSUS server to at least
that version or drop the database. WSUS was installed with SQL DB.
What do you suggest?
Thanks.
Please see full log:
2013-12-01 06:58:24 Postinstall started
2013-12-01 06:58:24 Detected role services: Api, Database, UI, Services
2013-12-01 06:58:24 Start: LoadSettingsFromXml
2013-12-01 06:58:24 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2013-12-01 06:58:24 Value is true
2013-12-01 06:58:24 End: GetConfigValue
2013-12-01 06:58:24 Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2013-12-01 06:58:24 Value is D:\sources\wsus
2013-12-01 06:58:24 End: GetConfigValue
2013-12-01 06:58:24 Content directory is D:\sources\wsus
2013-12-01 06:58:24 Start: GetConfigValue with filename=UpdateServices-DB.xml item=InstanceName
2013-12-01 06:58:24 Value is confman
2013-12-01 06:58:24 End: GetConfigValue
2013-12-01 06:58:24 SQL instance name is confman
2013-12-01 06:58:24 End: LoadSettingsFromXml
Post install is starting
2013-12-01 06:58:24 Start: Run
2013-12-01 06:58:24 Fetching WsusAdministratorsSid from registry store
2013-12-01 06:58:24 Value is S-1-5-21-1033354796-2088831985-1429053453-1003
2013-12-01 06:58:24 Fetching WsusReportersSid from registry store
2013-12-01 06:58:24 Value is S-1-5-21-1033354796-2088831985-1429053453-1004
2013-12-01 06:58:25 Configuring content directory...
2013-12-01 06:58:25 Configuring groups...
2013-12-01 06:58:26 Starting group configuration for WSUS Administrators...
2013-12-01 06:58:26 Found group in regsitry, attempting to use it...
2013-12-01 06:58:28 Writing group to registry...
2013-12-01 06:58:28 Finished group creation
2013-12-01 06:58:28 Starting group configuration for WSUS Reporters...
2013-12-01 06:58:28 Found group in regsitry, attempting to use it...
2013-12-01 06:58:28 Writing group to registry...
2013-12-01 06:58:28 Finished group creation
2013-12-01 06:58:28 Configuring permissions...
2013-12-01 06:58:28 Fetching content directory...
2013-12-01 06:58:28 Fetching ContentDir from registry store
2013-12-01 06:58:28 Value is D:\sources\wsus
2013-12-01 06:58:28 Fetching group SIDs...
2013-12-01 06:58:28 Fetching WsusAdministratorsSid from registry store
2013-12-01 06:58:28 Value is S-1-5-21-1033354796-2088831985-1429053453-1003
2013-12-01 06:58:28 Fetching WsusReportersSid from registry store
2013-12-01 06:58:28 Value is S-1-5-21-1033354796-2088831985-1429053453-1004
2013-12-01 06:58:28 Creating group principals...
2013-12-01 06:58:28 Granting directory permissions...
2013-12-01 06:58:28 Granting permissions on content directory...
2013-12-01 06:58:29 Granting registry permissions...
2013-12-01 06:58:29 Granting registry permissions...
2013-12-01 06:58:29 Granting registry permissions...
2013-12-01 06:58:29 Configuring shares...
2013-12-01 06:58:29 Configuring network shares...
2013-12-01 06:58:29 Fetching content directory...
2013-12-01 06:58:29 Fetching ContentDir from registry store
2013-12-01 06:58:29 Value is D:\sources\wsus
2013-12-01 06:58:29 Fetching WSUS admin SID...
2013-12-01 06:58:29 Fetching WsusAdministratorsSid from registry store
2013-12-01 06:58:29 Value is S-1-5-21-1033354796-2088831985-1429053453-1003
2013-12-01 06:58:29 Content directory is local, creating content shares...
2013-12-01 06:58:29 Creating share "UpdateServicesPackages" with path "D:\sources\wsus\UpdateServicesPackages" and description "A network share to be used by client systems for collecting all software packages (usually applications)
published on this WSUS system."
2013-12-01 06:58:29 Deleting existing share...
2013-12-01 06:58:29 Creating share...
2013-12-01 06:58:29 Share successfully created
2013-12-01 06:58:29 Creating share "WsusContent" with path "D:\sources\wsus\WsusContent" and description "A network share to be used by Local Publishing to place published content on this WSUS system."
2013-12-01 06:58:29 Deleting existing share...
2013-12-01 06:58:29 Creating share...
2013-12-01 06:58:29 Share successfully created
2013-12-01 06:58:29 Creating share "WSUSTemp" with path "C:\Program Files\Update Services\LogFiles\WSUSTemp" and description "A network share used by Local Publishing from a Remote WSUS Console Instance."
2013-12-01 06:58:29 Deleting existing share...
2013-12-01 06:58:29 Creating share...
2013-12-01 06:58:29 Share successfully created
2013-12-01 06:58:29 Finished creating content shares
2013-12-01 06:58:29 Stopping service WSUSService
2013-12-01 06:58:29 Stopping service W3SVC
2013-12-01 06:58:32 Configuring database...
2013-12-01 06:58:32 Configuring the database...
2013-12-01 06:58:32 Establishing DB connection...
2013-12-01 06:58:32 Checking to see if database exists...
2013-12-01 06:58:32 Database exists
2013-12-01 06:58:32 Switching database to single user mode...
2013-12-01 06:58:32 Loading install type query...
2013-12-01 06:58:32 DECLARE @currentDBVersion       int
DECLARE @scriptMajorVersion     int = (9600)
DECLARE @scriptMinorVersion     int = (16384)
DECLARE @databaseMajorVersion   int
DECLARE @databaseMinorVersion   int
DECLARE @databaseBuildNumber    nvarchar(10)
IF NOT EXISTS(SELECT * FROM sys.databases WHERE name='SUSDB')
BEGIN
    SELECT 1
END
ELSE
BEGIN
    SET @currentDBVersion = (SELECT SchemaVersion FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    SET @databaseBuildNumber = (SELECT BuildNumber FROM SUSDB.dbo.tbSchemaVersion WHERE ComponentName = 'CoreDB')
    DECLARE @delimiterPosition INT = CHARINDEX('.', @databaseBuildNumber)
    IF (@delimiterPosition = 0)
    BEGIN
        RAISERROR('Invalid schema version number', 16, 1) with nowait
        return
    END
    SET @databaseMajorVersion = SUBSTRING(@databaseBuildNumber, 1, @delimiterPosition - 1)
    SET @databaseMinorVersion = SUBSTRING(@databaseBuildNumber, (@delimiterPosition + 1), (10 - @delimiterPosition))
    IF @currentDBVersion < 926
    BEGIN
        SELECT 3
    END
    ELSE
    BEGIN
        IF (@scriptMajorVersion > @databaseMajorVersion OR
           (@scriptMajorVersion = @databaseMajorVersion AND @scriptMinorVersion > @databaseMinorVersion))
        BEGIN
            SELECT 2
        END
        ELSE IF (@scriptMajorVersion = @databaseMajorVersion AND
                 @scriptMinorVersion = @databaseMinorVersion)
        BEGIN
            SELECT 0
        END
        ELSE
        BEGIN
            SELECT 4
        END
    END
END
2013-12-01 06:58:33 Install type is: UnsupportedFuture
2013-12-01 06:58:33 DB is a higher version than the config scripts
2013-12-01 06:58:33 Swtching DB to multi-user mode......
2013-12-01 06:58:33 Finished setting multi-user mode
2013-12-01 06:58:33 Microsoft.UpdateServices.Administration.CommandException: The schema version of the database is from a newer version of WSUS
than currently installed. You must either patch your WSUS server to at least
that version or drop the database.
   at Microsoft.UpdateServices.Administration.ConfigureDB.CheckForUnsupportedVersion(DBInstallType installType, Boolean dbExists)
   at Microsoft.UpdateServices.Administration.ConfigureDB.ConnectToDB()
   at Microsoft.UpdateServices.Administration.ConfigureDB.Configure()
   at Microsoft.UpdateServices.Administration.PostInstall.Run()
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: The schema version of the database is from a newer version of WSUS
than currently installed. You must either patch your WSUS server to at least
that version or drop the database.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Gerry,
1. I uninstalled WSUS, removed DB, restarted. And reinstall WSUS again. This time MS Management Console of WSUS could not be started. I did it after WSUS was added following your blog pix.
I checked c:\program files\update services, there were couple of missing directories by comparison what was in case when I installed WSUS after SQL but before CM: Tools, Shema, and another A.. something. I saw this issue on NOOB. And people copied these
directories from previous installation.
How we can explain this behavior on RTM version?
Then I uninstalled it again. And give another try... Here I found another interesting thing. Please compare your slide number 5 from your link and attached one. You can see that on Add Roles and Features Wizard page are missing items. Some
of them were found in next screen of my installation (I am using RTM server) but one API and Power shell cmdlets were not listed on final screen before start install. May be those are note important...
I reinstall again... and the MS Management Console fails again. Exactly the same thing that I saw during 2 weeks of trying to make works. Don't see what I can screw up here.
What about missing directories after reinstalling WSUS. Is that normal? And in IIS there is no WSUS.
I don't see here any difficult thing, just simple wizard... But it not works. Second CM server.
What I do wrong here to create a failure of MMC. There is any blog with examples of RTM Server 2012 and CM RTM. All stuff is 2012. So kind of guesses and no precise thing to do...
Sorry for my cry :). The only solution is to call MS and pay $250 for SUCH a trivial thing that not works.
Any help? Please see pics. Can you confirm that you have the same or more directories in Update Services
Thanks.
API and Power Shell Cmdlets feature missed if compare with yours slides.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Fatal error on Premiere Elements 3.02 when loading any project (new ones included)

Similar Messages

Maybe you are looking for