Organizer issue with PSE10

I have been using PSE 10 with no problems. Today I bought several new digital elements (different places) and the import fails on each one saying the file type is not supported or they are already in the catalog. These are new so they are not in the catalog. The file types are png, jpg and psd so they should work fine. What do I need to do to fix this?

Do these file open in PSE Editor?
Please ensure that the filenames have no extra dots or invalid characters.
Thanks

Similar Messages

Organizer Issue with Zen Mi

A short time ago each time the Zen was powered up it began to "Rebuild The Library".
I called Customer Support and was told to transfer all files to the PC hard disk, then reformat, then transfer the files back.
This fixed the initial problem and the Zen works normally, but now the Organizer will not work. It now only shows a DOS directory structure with the Artist at the highest level. The next level is the Album and then the Track. It is pretty much unusable. Want it to perform as before.(It had four windows in the center frame with Genre, Artist and album windows on the left and Title on the right, all of which I could configure.)
I called the support line four times and was unable to solve the problem. I upgraded to the latest firmware and latest Organizer and Explorer. The last call the direction was to transfer the files, format and transfer back. Nothing has worked.
Any ideas?

Thanks for the info. I installed the previous firmware version ..0 and all works normally. Also the PlaysForSure files work. Not sure of any advantage with the PlaysForSure firmware as the organizer becomes virtually unusable.

Issues with trying to Sync of BB Tourch 9800 Organizer with MS Outlook 2010 (64Bit) using BB DM Ver 6.1.0.36 Bundle 38

I am having ongoing issues with trying to sync contacts, memos calendar etc using the latest version of DM 6. I have uninstalled and reinstalled the DM software. I have tried to "remap" the fields as noted in the error messages only to get other error messages including: "intellisync one or more configured folders is not available"
I have on many occasions tried to reset the organizer in DM6, checking the box for calendar, address book etc only to go through the process of selecting MS Office and to complete the set up and then the check box is "unchecked" automatically. ( I must be doing something wrong)
I have reviewed different KB fixes without any success - I may be able to re-sync after doing a suggested change but it will only work once they I am back to the same problem of not being able to sync my calendar etc.
I have changed the WIN7 administrator levels as suggested.
I am running Win 7 and MS Office Professional 2010 (64 Bit) which the latest version of DM 6 is supposed to work with.
Any suggestions on how to get my organizer to stat syncing again?

yes try click "sync"at bottom right

I have a "Contact" organization issue I need help with. I organize multiple customers under their account affiliation. I place the people with their contact info under each account name by their dept/role in the notes section of their account. I am l

I have a "Contact" organization issue I need help with. I organize multiple customers under their account affiliation. I place the people with their contact info under each account name by their dept/role in the notes section of their account. I am looking to be able to directly dial / email from this info in yet notes section located within a contact. On Blackberry, the notes area entered in a contact can connect directly but on the iPhone those numbers/emails are inactive. I am trying to avoid having to create each of these individuals as a separate contact and keep them under their account affiliation. It is easier to find them. This does not seem like that complicated of a request and hoping someone can tell me how or share an app that will enable the "notes" within a contact be "active". Hope this makes sense.

I seem to recall that this question has been asked before and I'm pretty sure that the answer is that you can't do what you want to do with the native contact app. However, there are lots of contact apps out there that pull from the built app's data but have other features. Perhaps one of them would meet your needs.

Crash issues with elements organizer while running Apple OS 10.9 Mavericks

Crash issues with elements organizer while running Apple OS 10.9 Mavericks. Crashes then ask if you want to reopen or not. Also when you are trying to manuver the page with your mouse things go crazy from a full page edit back to viewing all photos on the site and skipping around from picture to picture. Unsusable as it is today!

It is very critical to delete all preferences when you do a major OS X upgrade. You need to go to your username>library>preferences and delete everything pertaining to PSE. To see that library in 10.9, open a finder window, click your user account in the list on the left (the little house with your name), and then click the gear wheel at the top of the window and choose View Options. At the bottom of the list of checkboxes you'll see Library. Turn it on and then you can easily find the preferences folder.

Issues with Organizational Model in CRM

Hi guys,
           We are implementing CRM 5.0 and I generated Organizational Model in system using Report: CRM_ORGMAN_R3_ORGDATA_GENERATE. This report generated organizational model with no errors. But there is a issue with org model:
In our R/3 system same sales office are assigned to multiple sales area and same salesgroups are assigned to multiple sales office due to this in CRM when the org model generated it only assigned the sales office and sales group to sales org 1000 however sales org 2000 and 3000 left unassigned.
eg:
R/3:
Sales office assigned to
sales area: 1000   10   10
                       001
                       002
                       003
                 2000   10   10
                      001
                      002
                      003
And after generation in CRM:
Sales org: 1000
                  sales office: 001
                                    002
                                    003
Sales org: 2000
                   no sales office or sales org assigned.
When I am trying to create it manually then it gives me an error: "attribute_R/3_SA_ORG with value xyx already assigned".
Did anybody faced similar issue?
I even ran the report for to change the org model to enhanced version but it didnt helped.
Please give your suggestions.
Thanks
Ankit

Hi Ankit,
Its common that the sales office are only assigned to the first sales organiz unit in
CRM structure in PPOMA_CRM. The same for the sales groups that are only assigned under the first sales office unit in CRM structure in PPOMA_CRM.
No mather, the important thing is that under Function tab > Sales office tab, for a sales office, the system has all the possible combinations for R/3 sales org, R/3distribution channel and R/3 division.
And the same under Function tab > Sales group tab, for a sales group, that must contain the possible combinations for R/3 sales org, R/3 sales office, R/3distribution channel and R/3 division.
In this way, you have the structure like:
SALESORG1001
   SALESOFFICE 1100
       SALESGROUP 100
   SALESOFFICE 1200
   SALESOFFICE 1300
SALESORG1002
SALESORG1003
But inside SALESOFFICE 1100 details you have something like:
Sales office tab:
R3 sales org | R3 DC | R3 Div
1001              10         01
1002              10         01
1003              10         01
And under Sales Group 100 you have something like:
Sales group tab:
R3 sales org | R3 Sales Office | R3 DC | R3 Div
1001              1100                  10         01
1002              1100                  10         01
1003              1100                  10         01
1001              1200                  10         01
1002              1200                  10         01
1003              1200                  10         01
1001              1300                  10         01
1002              1300                  10         01
1003              1300                  10         01
Hope it helps,
Susana Messias

Issue With Page Break When Sorting is also applied on group

Hi
I am facing an issue with Page break only when I have sorting applied on the grouping that I have in the template.
The following is the sample XML
<ROWSET>
<ROW>
<GRE>org1</GRE>
<ORGANIZATION>Accounts</ORGANIZATION>
<FULL_NAME>test1,</FULL_NAME>
<ELEMENT_NAME>TEST BONUS</ELEMENT_NAME>
<CLASSIFICATION>Supplemental Earnings</CLASSIFICATION>
<RUN_VALUE>250</RUN_VALUE>
<MONTH_VALUE>500</MONTH_VALUE>
<QUARTER_VALUE>500</QUARTER_VALUE>
<YEAR_VALUE>500</YEAR_VALUE>
</ROW>
<ROW>
<GRE>org1</GRE>
<ORGANIZATION>Finance</ORGANIZATION>
<FULL_NAME>test2</FULL_NAME>
<ELEMENT_NAME>VOLUNTARY AD AND D</ELEMENT_NAME>
<CLASSIFICATION>Voluntary Deductions</CLASSIFICATION>
<RUN_VALUE>5.19</RUN_VALUE>
<MONTH_VALUE>10.38</MONTH_VALUE>
<QUARTER_VALUE>10.38</QUARTER_VALUE>
<YEAR_VALUE>10.38</YEAR_VALUE>
</ROW>
<ROW>
<GRE>org1</GRE>
<ORGANIZATION>Finance</ORGANIZATION>
<FULL_NAME>test3</FULL_NAME>
<ELEMENT_NAME>HMO MEDICAL</ELEMENT_NAME>
<CLASSIFICATION>Pre-Tax Deductions</CLASSIFICATION>
<RUN_VALUE>19.67</RUN_VALUE>
<MONTH_VALUE>39.34</MONTH_VALUE>
<QUARTER_VALUE>39.34</QUARTER_VALUE>
<YEAR_VALUE>39.34</YEAR_VALUE>
</ROW>
<ROW>
<GRE>org1</GRE>
<ORGANIZATION>Finance</ORGANIZATION>
<FULL_NAME>test4</FULL_NAME>
<ELEMENT_NAME>PENSION NR DC</ELEMENT_NAME>
<CLASSIFICATION>Pre-Tax Deductions</CLASSIFICATION>
<RUN_VALUE>0</RUN_VALUE>
<MONTH_VALUE>360</MONTH_VALUE>
<QUARTER_VALUE>360</QUARTER_VALUE>
<YEAR_VALUE>360</YEAR_VALUE>
</ROW>
</ROWSET>
In the template I group the data based on CLASSIFICATION and then sort on the same column CLASSIFICATION. I have a page-break applied for every group.
When I generate the PDF, I am not getting the page-breaks for every group. Instead some of them are displayed in the same page.
But when I remove the sorting that I had in the template on the column CLASSIFICATION, I am getting the output in the desired way but not in a sorted order.
kumar

Hi All,
I am using MS-WORD 2007 and BI Publisher desktop 10.1.3.3.3.
When I use split-by-page-break, splitting is performed for every line .. but not for group of lines.
Can anybody throw some light on this?
FYI...
I am using this code:
?if: position() mod 6= 0?
?split-by-page-break:?
?end if?
(Of course with in tags)
in G_LINES loop.
Can anybody help me out :-(
--Saritha

Issues with using utl_http with Oracle Wallet

Hello Everyone,
We are experimenting with Oracle wallet and utl_http and are attempting to do an https transfer and we are facing some problems. I will appreciate your help greatly if you can advise on what could be wrong. We are on db version 10.2.0.1 and Unix HP-UX. The intention ping an https url and get a simple 200 response. Future development would include get/post XML documents from that url and other interesting stuff. I understand that utl_http with Oracle wallet can be used for this purpose.
The wallet has been created and the ewallet.p12 exists. We downloaded the SSL certificate from the url's website and uploaded into the wallet.
Everything works if I put in a url with plain http. However, it does not work with an HTTP*S* url.
With HTTPS when I run the below code I get the following error. Again, greatly appreciate your time and help because this is the first time we are using Oracle wallet manager and do not know where to go from here.
ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1029
ORA-29268: HTTP client error
declare
url varchar2(225);
req utl_http.req;
resp utl_http.resp;
my_proxy BOOLEAN;
name varchar2(2000);
value varchar2(2000);
V_proxy VARCHAR2(2000);
v_n_proxy varchar2(2000);
v_msg varchar2(100);
v_len PLS_INTEGER := 1000;
BEGIN
-- Turn off checking of status code.
utl_http.set_response_error_check(FALSE);
--Set proxy server
utl_http.set_proxy('my-proxy');
utl_http.set_wallet('file:<full Unix path to the wallet on DB server>','wallet998');
req := utl_http.begin_request('https://service.ariba.com/service/transaction/cxml.asp');
--Set proxy authentication
utl_http.set_authentication(req, 'myproxyid', 'myproxypswd','Basic',TRUE); -- Use HTTP Basic
resp := utl_http.get_response(req);
FOR i IN 1..utl_http.get_header_count(resp) LOOP
utl_http.get_header(resp, i, name, value);
dbms_output.put_line(name || ': ' || value);
END LOOP;
utl_http.end_response(resp);
exception
when others then
dbms_output.put_line(sqlerrm);
END;

I tried this using plsql ...
declare
SOAP_URL constant varchar2(1000) := 'http://125.21.166.27/cordys/com.eibus.web.soap.Gateway.wcp?organization=o=WIPRO,cn=cordys,o=itgi.co.in';
request UTL_HTTP.req;
begin
dbms_output.put_line('Begin Request');
request := UTL_HTTP.begin_request(SOAP_URL,'POST',UTL_HTTP.HTTP_VERSION_1_1);
dbms_output.put_line('After Request');
exception
when others then
dbms_output.put_line('Error : '||sqlerrm);
end;The output was ...
Begin Request
Error : ORA-29273: HTTP request failed
ORA-06512: at "SYS.UTL_HTTP", line 1029
ORA-12535: TNS:operation timed outIt seems to be an issue with the webservice, plz check if its available & allowing requests.

PSE 11 and PS CC issues with import/open and saving

Good afternoon,
I have had PSE 11 for several months but have hardly touched it due to two problems. When I try to import images into the organizer, if I choose any location other than the default that opens, the whole program freezes and I have to force quit to get out of it. I have been able to open files by going to File - get photos and videos - by searching....When I can get them, they load at snail speed. I've done a few projects and when I go to save, I have the same issue. This has caused me to loose several projects as again, the whole program freezes and I have to force quit.
I just signed up for the photographer's black Friday deal and downloaded PS. I am having the same issue. If I go to open a file in PS and choose anywhere other than the default location, the box closes immediately and I can't get anything to open. Thankfully, the program doesn't freeze up like PSE 11, but this is so frustrating. I have Lightroom and have issues there too. What is going on!
Thanks
JP

I am having a similar issue with photoshop CC. I am on a mac and just upgraded to maverick (
OS X 10.9 (13A603)) and since the update any time I want to open or place a file it closes the window.
Something worse happened on windows 8.1 when I upgraded that OS Illustrator and photoshop just crashed once it was open. I had to uninstall and reinstall both applications and it worked.
I tried the same thing on the mac and uninstalled photoshop, then reinstalled it but I that did not resolve the issue. I have a video of what it is doing. The two workarounds I found was to drag the images into photoshop or create a new file then go to file open which you will see in the video.
If there is a fix for this please let me know, it is very frustrating!
Regards

[SOLVED]Issue with Postfix sending to external mail addresses

I'm having a very silly issue with Postfix. I followed the wiki article at [link]https://wiki.archlinux.org/index.php/Postfix[/link], and everything seems to work properly, however I cannot send to emails outside of my domain.
I get the error:
550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!
Here is what the logs say:
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: connect from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: client=localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: 091E011E3C: reject: RCPT from localhost.localdomain[127.0.0.1]: 550 5.1.1 <[email protected]>: Recipient address rejected: Local delivery only!; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<sendingdomain.com>
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: lost connection after RCPT from localhost.localdomain[127.0.0.1]
May 08 16:05:12 my.dns.stuff.org postfix/smtpd[31464]: disconnect from localhost.localdomain[127.0.0.1]
May 08 16:05:14 my.dns.stuff.org sudo[31476]: me : TTY=pts/0 ; PWD=/etc/postfix ; USER=root ; COMMAND=/usr/bin/journalctl
main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/BASIC_CONFIGURATION_README.html etc.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/bin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/lib/postfix
# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
data_directory = /var/lib/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
myhostname = mail.sendingdomain.com
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
mydomain = www.sendingdomain.com
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
myorigin = $mydomain
append_dot_mydomain = no
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
inet_interfaces = all
#inet_interfaces = loopback-only
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = localhost
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
default_transport = error: Local delivery only!
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
alias_maps = hash:/etc/postfix/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
alias_database = $alias_maps
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
# Cyrus IMAP over LMTP. Specify ``lmtpunix cmd="lmtpd"
# listen="/var/imap/socket/lmtp" prefork=0'' in cyrus.conf.
#mailbox_transport = lmtp:unix:/var/imap/socket/lmtp
# Cyrus IMAP via command line. Uncomment the "cyrus...pipe" and
# subsequent line in master.cf.
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/bin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /etc/postfix/sample
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
inet_protocols = ipv4
#virtual_mailbox_domains = sendingdomain.com
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf
virtual_mailbox_base = /home/vmailer
virtual_uid_maps = static:5003
virtual_gid_maps = static:5003
virtual_minimum_uid = 5003
virtual_mailbox_limit = 51200000
Any help would be appreciated. Thank you.
Last edited by nadman10 (2014-05-14 14:36:10)

Your main.cf seems redundant.
For example:
if you specify:
virtual_alias_maps = hash:/etc/postfix/virtual_alias, mysql:/etc/postfix/mysql_virtual_forwards.cf
you don't need this:
alias_maps = hash:/etc/postfix/aliases
and i think you have a lot of more options you don't need.
This is my main.cf on my vps and everything works great (sending and receiving emails from/to most common mail server: gmail, hotmail etc etc)
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
readme_directory = no
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
message_size_limit = 4194304
virtual_mailbox_domains = mysql:/etc/postfix/mysql-virtual-mailbox-domains.cf
virtual_mailbox_maps = mysql:/etc/postfix/mysql-virtual-mailbox-maps.cf
virtual_alias_maps = mysql:/etc/postfix/mysql-virtual-alias-maps.cf
virtual_transport = dovecot
dovecot_destination_recipient_limit = 1
it is very simple (no dkim, no forced tls, no mailbox limits and so on) and it can be improved but it works..
as I suggested you just try spending some hour wiping postfix installation and giving a look to this guide

I have found an issue with MS13-098 which causes systems to be renamed to MINWINPC

I have found an issue with MS13-098 which causes systems to be renamed to MINWINPC. The issue has been reported in Japanese by Microsoft. The translation is:
Phenomenon
In Windows Server 2008 or Windows Vista, you might not be able to log an error appears to apply the new update the following programs, if you try to log on after the restart. • MS12-024 (KB2653956)
• MS13-098 (KB2893294)
Error message displayed is as follows.
Incorrect password or user name
Back to the top | feedback
Collapse image Cause
This behavior occurs when you apply the update KB2653956 in the state of some data is damaged following registry key, or does not exist.
HKEY_LOCAL_MACHINE \ SCHEMA \ wcm :/ / Microsoft-Windows-CoreOS? ...
Any string will contain the part of the ... Note:. Also, make sure to load the SystemRoot% \ system32 \ SMI \ Store \ Machine \ SCHEMA.DAT file% if the HKEY_LOCAL_MACHINE \ SCHEMA does not exist.
When you apply the update of KB2653956 in the state where the registry key is not present, the value of the following registry is changed to MINWINPC, logon will not be able to.
• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ ComputerName \ ActiveComputerName
• HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ ComputerName \ ComputerName
Back to the top | feedback
Collapse image Solution
If this occurs, change to the correct computer name the value of the ComputerName registry and ActiveComputerName start in safe mode, has been mentioned above, and then restart.
Back to the top | feedback
Collapse image Workaround
To prevent this phenomenon occurs, you download and run the System Update Readiness Tool from the following KB.
http://support.microsoft.com/kb/947821
By performing the system update Preparation tool registry that is described in Section Symptoms are repaired.
If the repair is made, starting with log Recreated missing key as the following WinDir% \ Logs \ CBS \ CheckSUR.log file% is recorded.
Recreated missing key:? Wcm :/ / Microsoft-Windows-CoreOS ... \ metadata \ elements \ ComputerName
In addition, regardless of the presence or absence of entry damaged Microsoft-Windows-CoreOS, you can set the value of the ComputerName key in this tool. For this reason, the following log is recorded in the CheckSUR.log.
Recreated value: @ _type.
Recreated value: @ dataOnly.
Recreated value: @ default.
Recreated value: @ description.
Recreated value: @ displayName.
Recreated value: @ handler.
Recreated value: @ legacyName.
Recreated value: @ legacyType.
Recreated value: @ migrate.
Recreated value: @ scope.
Recreated value: @ xsd: type.
Back to the top | feedback
Note: This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. It contains information in response to emerging issues are listed. As a result of the speed of information provided may be
typographical errors are included in the article, you might be revised at any time without prior notice. For other considerations, and use conditions
Please refer to.
Back to the top | feedback
Collapse image Property
December 11, 2013 - Revision: - Last Review: 2901584: 4.0 Document Number
This document that was written about products for.
• Windows Vista Business
• Windows Vista Business 64-bit edition
• Windows Vista Enterprise
• Windows Vista Enterprise 64-bit edition
• Windows Vista Home Basic
• Windows Vista Home Basic 64-bit edition
• Windows Vista Home Premium
• Windows Vista Home Premium 64-bit edition
• Windows Vista Starter
• Windows Vista Ultimate
• Windows Vista Ultimate 64-bit edition
• Windows Server 2008 Datacenter
• Windows Server 2008 Datacenter without Hyper-V
• Windows Server 2008 Enterprise
• Windows Server 2008 Enterprise without Hyper-V
• Windows Server 2008 for Itanium-Based Systems
• Windows Server 2008 Foundation
• Windows Server 2008 Standard
• Windows Server 2008 Standard without Hyper-V
• Windows Web Server 2008
• Windows HPC Server 2008
• Windows Essential Business Server 2008
We are having the issue on hundreds of systems and I am rolling out the readiness tool mentioned above to prevent other systems from being affected. In the mean time I have stopped deploying MS13-098 and am hoping Microsoft will go ahead and let all
of their customers know about the problem instead of just one country. Hopefully the original bulletin will be updated with this known issue.

PPoj,
Apple has offered replacement or pro-rated refunds in the US as a settlement of a class action lawsuit, not because of pride in their design-centric approach to their products. If you seek a similar replacement/refund program in India, then the odds are pretty good that you’d need a similar legal approach with which to convince Apple to offer a similar program there. If you’re unwilling to wait for such an event, then you can purchase a replacement power cable now, and hope for a pro-rated refund at some point in the future.

Issues with Shockwave 11.5.2.602 / 11.5.6.606 MSI installer

<UPDATE 8/3/09> Nearly all of the issues mentioned below are still present in the MSI installer for 11.5.6.606 - the only one that Adobe have fixed is the one where the MozillaPlugins 'Version' value is left blank by the MSI by default - this is now created correctly, but all of the other issues remain.
Personally I have given up trying to use this MSI package to deploy Shockwave until Adobe get their act together - instead I am using a wrapper to wrap the Shockwave executable inside an MSI file and deploying it that way, although this is not ideal.
I have created an MST file which will fix the MSI installer for version 11.5.6.606, which I will post to another forum shortly, but I am not planning to keep it updated for future versions as I don't really have the time.
Hi,
I've tried submitting the following via the Adobe Customer Support portal and via the Feature Request/Bug Report form, but the first told me that I needed to 'get in touch with Adobe Enterprise Solutions team for getting help' and that 'to get in touch with them you have to purchase a contract', and the second resulted in a bounced email address saying that '[email protected]' 'does not exist at the organization this message was sent to'.
In short, attempting to contact Adobe to report issues with their installers sucks, and I am posting this here in the vain hope that someone at Adobe might read this message and possibly forward it to the relevant people. Some of the issues have already been reported here on this forum, but some of them are new, and I guess others might be interested in them too.
Hi,
I would like to report some issues with most recent version of the Shockwave installer, available in MSI format from the following location:
http://www.adobe.com/cfusion/entitlement/index.cfm?k=4E6102EB-DA7C-2795-C744826EFDE2A098&l oc=en_us
This is the installer for version 11.5.2.602, with a digital signature dated 06 November 2009 10:52:21
When downloading this version of the installer in Windows Installer (MSI) format, the following issues manifest themselves, most of which are not a problem when using the Full EXE installer available from the same page.
First of all, when installing the MSI file using Group Policy Software Deployment, if you log on to the computer after the MSI file has been deployed and view a web page that contains Shockwave content, you receive the following errors in the Windows event log:
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1004
Date: 16/12/2009
Time: 16:51:23
User: CRGS\DefaultUser
Computer: ITO01
Description:
Detection of product '{7D0F2155-D7D3-42CE-903F-684ADD77FF89}', feature 'Adobe_Shockwave_Player_', component '{E89F323D-7BDB-46E1-A0FD-6227821F94EA}' failed. The resource 'C:\WINDOWS\system32\config\systemprofile\Application Data\Adobe\' does not exist.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Type: Warning
Event Source: MsiInstaller
Event Category: None
Event ID: 1001
Date: 16/12/2009
Time: 16:51:23
User: CRGS\DefaultUser
Computer: ITO01
Description:
Detection of product '{7D0F2155-D7D3-42CE-903F-684ADD77FF89}', feature 'Adobe_Shockwave_Player_' failed during request for component '{3D3697FC-DB90-46D8-9ED4-5D54B4901F62}'
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
If you are logged on as an Administrator, then the computer will immediately attempt to 'repair' the Adobe Shockwave Player installation in order to create the missing folder 'C:\WINDOWS\system32\config\systemprofile\Application Data\Adobe\', which leads to a significant delay in the initialization of the Shockwave content on the web page. If you are logged on as a non-Administrator, the errors will still appear, but the 'repair' operation will fail due to insufficient permissions to create the above folder.
I have done some testing and it seems as if this problem can be easily resolved by removing the code from the installer which tells it to create an empty folder in the 'Application Data' folder called 'Adobe\Shockwave Player 11'. This code seems to be entirely unnecessary, as no files are created inside this folder as part of the installation, and I have removed it successfully from my own copy of the MSI without it causing any issues. I have found some other people who are also experiencing this problem in the following forum post:
http://forums.adobe.com/message/2379350 (post number 8)
and since this 'repair' operation causes all customised registry settings to be reset back to defaults as part of the repair, it would be very helpful if this 'feature' could be removed from future versions.
Secondly, there are a number of registry keys which are created incorrectly by the MSI installer when the above 'repair' operation takes place, which need to be corrected to prevent further issues from occurring:
Under '[HKEY_CLASSES_ROOT\CLSID\{1F3CB77D-D339-49e0-B8E4-FECD6D6F8CB8}\LocalServer32]', the 'default' value is set to the following by the MSI:
C:\WINDOWS\system32\Adobe\SHOCKW~1\SWHELP~1.EXE"
(Please note that there is a double quotation mark at the end of the value, but not at the beginning)
Whereas the executable installer creates the value as follows:
"C:\WINDOWS\system32\Adobe\Shockwave 11\SwHelper_1152602.exe"
According to a forum post (http://forums.adobe.com/message/2379350, post 15), this causes DCOM errors when Shockwave is launched, if the MSI 'repair' has taken place as described above.
The above registry value should be set to the following in the installer's Registry table:
"[INSTALLDIR]Shockwave 11\SwHelper_1152602.exe"
so that the MSI installer works the same as the executable one.
Under '[HKEY_CLASSES_ROOT\TypeLib\{6EF568F4-D437-4466-AA63-A3645136D93E}\1.0\0\win32]', the 'default' value is set to the following by the MSI:
Adobe\SHOCKW~1\SWHELP~1.EXE
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Adobe\Shockwave 11\SwHelper_1152602.exe
Also, under '[HKEY_CLASSES_ROOT\TypeLib\{6EF568F4-D437-4466-AA63-A3645136D93E}\1.0\HELPDIR]', the 'default' value is set to the following by the MSI:
Adobe\SHOCKW~1\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Adobe\Shockwave 11\
Once again, the above registry values should be set to the following in the installer's Registry table to fix the issue:
[SystemFolder]Adobe\Shockwave 11\SwHelper_1152602.exe
[SystemFolder]Adobe\Shockwave 11\
Under '[HKEY_CLASSES_ROOT\CLSID\{166B1BCA-3F9C-11CF-8075-444553540000}]', the 'default' value is NOT SET by the MSI by default:
Whereas the executable installer creates the value as follows:
Shockwave ActiveX Control
This value should be set in the installer's Registry table to fix the issue.
Under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\common]', the 'default' value is set to the following by the MSI:
Macromed\common\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\common\
Also, under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\coreplayer]', the 'default' value is set to the following by the MSI:
Macromed\Shockwave 10\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\Shockwave 10\
Also, under '[HKEY_LOCAL_MACHINE\SOFTWARE\Macromedia\Shockwave 10\location\coreplayerxtras]', the 'default' value is set to the following by the MSI:
Macromed\Shockwave 10\xtras\
Whereas the executable installer creates the value as follows:
C:\WINDOWS\system32\Macromed\Shockwave 10\xtras\
The above registry values should be set to the following in the installer's Registry table to fix the issue:
[SystemFolder]Macromed\common\
[SystemFolder]Macromed\Shockwave 10\
[SystemFolder]Macromed\Shockwave 10\xtras\
The MSI installer does not create '[HKEY_CLASSES_ROOT\.dcr]', '[HKEY_CLASSES_ROOT\.dir]', or '[HKEY_CLASSES_ROOT\.dxr]'
Wherease the executable installer creates all three of these keys and populates them all with the following 'default' value:
"Content Type"="application/x-director"
These keys and values should be set in the installer's Registry table to fix the issue.
The MSI installer creates a value under the following registry key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponets\SwDi r]
However this registry key is obviously misspelt (missing an 'n' in 'OptionalComponets') and should read as follows:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OptionalComponents\SwD ir]
This key name needs to be changed in the installer's Registry table to fix the issue (also pointed out in the following forum post: http://forums.adobe.com/message/2379350 (post number 10)).
Under [HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer], the 'Version' value is left blank by the MSI by default:
Whereas the executable installer creates the value as follows:
1152602
This registry value should be set to the correct version in the installer's Registry table to fix the issue.
Finally, the MSI installer creates a number of registry values under the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer\Mime Types]
These values are *in addition* to the values created under the following path:
[HKEY_LOCAL_MACHINE\SOFTWARE\MozillaPlugins\@adobe.com/ShockwavePlayer\MimeTypes]
(Note there is no space between 'Mime' and 'Types' in the second key path)
The executable installer *only* creates registry keys under the 'MimeTypes' key, and it seems as if this is the correct formatting for the key (also pointed out in the following forum post: http://forums.adobe.com/message/2379350 (post number 11)).
The unnecessary 'Mime Types' registry keys and values should be removed from the installer's Registry table to avoid any potential issues.
I am sorry that this is such a long list, but it seems as if a number of things have been changed in the transition from 11.5.1.601 to 11.5.2.602, and it would be very helpful if these changes could be put back to how they were before, so that the MSI and the executable installers function in the same way as much as possible.
Message was edited by Borgquite - added 11.5.6.606 update

Have posted an updated version of the MST to my webspace here:
http://homepage.ntlworld.com/minkus/shockwave/shockwave115606mst2.zip
This new version fixes the following issues (changes to this version in bold):
MsiInstaller repair & errors on first run as non-admin (removes 'AppData' directory entries)
DCOM errors once Shockwave is installed (adds double quotes to the beginnning of LocalServer32 value)
Incorrect TypeLib paths in the registry (fixed to use built-in [SystemFolder] property)
Default CLSID description value missing (set to 'Shockwave ActiveX Control', as per the executable installer)
Incorrect Shockwave 10 paths in the registry (fixed to use built-in [SystemFolder] property)
Misspelt 'OptionalComponets' registry key (renamed to 'OptionalComponents')
Missing .dcr, .dir, .dxr Content Type registry values (included in the executable installer)
Fixed incorrect AppID registry key (set to use installer's [VERSION] variable)
Removed 'Launch SWDNLD.exe' shortcut created in Programs subfolder (people don't want this - see here)
I have tested this on my network and it all seems to work fine. Unfortunately my original plan to use the executable installer didn't work out as it does not include the Shockwave 10 compatibility components described here and here, so it looks like I'll have to keep this MST file up to date with the latest versions until Adobe fix the problems themselves...
If you want to see the changes that I have made, load up Adobe's 11.5.6.606 MSI file in Orca, then use Transform / Apply Transform to apply the MST, and look for the entries in green.
Please post any feedback to this thread, and I will try to respond if I can help!
Chris Hill

Issue with Opening a PDF file

We have just completed an upgrade of one of our servers executing Reporting Services.   The upgrade was from 2005 to 2008.
After we have rendered a report and have it saved in PDF format, we start having issues.
If we try to open the PDF by double clicking on the file name in Windows Explorer, Adobe Reader starts, but sits unresponsive and consumes an excessive amount of CPU cycles.    It never completes the open and we have to kill the Adobe Reader process in Task Manager.
If we start Adobe Reader, and then use the Menu to do FIle -> Open, the PDF file opens immediately.
We have attempted both methods using several different versions of Adobe Reader.    The issue occurs on all versions prior to 9.3.
Since we are a service organization, we are unable to force our clients to upgrade to a more current version of Adobe Reader without providing assurances that this will correct this issue.
Has anyone else seen this type of issue with opening PDF files rendered by Reporting Services?   And if so, what is the cause and how did you correct it?
Thanks
Steve

Hi there,
Please find attached a word document which contains the error that comes up when I try to open the PDF file. This PDF was e-mailed to me from one of the Safety companies that I receive e-mails from on a regular basis. I believe I am running Windows XP and the version of Adobe is Adobe Reader X. I hope this is enough info for you.
Janice Nadeau
[signatue deleted by host]

Adobe 9 issues with forms in Acrobat Reader 7

I've been reading up on this forum as to why the adobe rights are disabled after a user saves their data in Reader. I have been adding form fields in Adobe Standard 9 then save the file, test it in Reader, then Extend the Forms Fill-In for Adobe Reader and save the file with a slightly different name. The only usage rights that are allowed is to Save Form Data. When I test the file in Reader 7, I can save the data but when I go into the document to make sure my data is there, I get that dreaded and popular message "Adobe Rights have changed and are no longer valid dialog box...
I never changed the original extended file to cause this..even when I don't add data but save to a new file anyway I lose the writable functionality.
A side note, I do not use LiveCycle and have been asked not to when creating these forms.
I did not have any problems with the forms that I had other people create and extend in Adobe Pro 8. It seems to be a Standard 9 and Pro 9 problem. Or, it could very well be me!
I use Reader 7 to test because these forms are for a volunteer organization and there are users on some early versions of Reader. II do not use earlier versions of Reader. This doesn't seem to be an issue in Reader 9. I cannot vouch for Reader 8.
I just had one of my form writers take my form that was done in Standard 9 and Extend Forms Fill-In via Adobe Pro 8. She initally received a message stating that the file appears to use a new format and it may not open or display correctly. I then got that same message when opening the extended version of the file. The document rights on the new form allow me to add comments and markup, a digital signature and save form data. Once I fill out the fields and try to save, also get another dialog box telling me that I need Adobe Standard or Professional to save (in this case it was 7 since I'm testing in Reader 7).
The forms that I am creating are initally PDFed by another party. The orignal forms are created in QuarkXpress 4.1 and PDFed using Acrobat Distiller 4.0 for Macintosh. I retrieve the files from a web site and save them to my hard drive to work on them. They are shared via email.
Any help would be greatly appreciated. I've spent the last week researching but no anwers to help me solve this particular issue with 9.

Interesting. I did just do the Reduce File Size and extended the document and there were no dialog boxes when I saved my data. The file size got larger instead of smaller and I received the message at the end of the Reduce File Size cycle that said " Enforcement of compatability to an earlier version of Acrobat has increased the size of some images". There is an image in the file, not one that I added, but from the original document. No change to the image either. No biggie to me. As long as my users can fill out the form and come back to it later to make changes, I'm happy!
Thank you. I think that solved it!

Issues with Photoshop Elements 12

I am already using Photoshop CS6 and was informed that I can also purchase and install Photoshop Elements 12 on the same PC (Windows 7).
This I have now done but after some installation issues I am now experiencing a problem with the camera raw part of Elements. I am receiving an error message when I try and send the edited raw file to the main Elements program. The strange part is that if I open the same raw file again in Elements camera raw and try transfering again it works OK. Can there be a conflict somewhere?

Hi,
Could you tell if you are facing this issue with Elements Organizer or Editor?
For Editor not launching,
If on Windows, could you follow the steps shared at: Photoshop Elements (PSE) knowledge base.
For MAC, Photoshop Elements (PSE) knowledge base.
For Organizer not launching,
For Windows, Photoshop Elements (PSE) knowledge base.
For MAC, Photoshop Elements (PSE) knowledge base.
Regards,
vaishali

Organizer issue with PSE10

Similar Messages

Maybe you are looking for